Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
5c5aff98
Commit
5c5aff98
authored
Mar 20, 2019
by
David Sterba
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
btrfs: remove unused parameter fs_info from emit_last_fiemap_cache
Signed-off-by:
David Sterba
<
dsterba@suse.com
>
parent
033774dc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
3 deletions
+2
-3
fs/btrfs/extent_io.c
fs/btrfs/extent_io.c
+2
-3
No files found.
fs/btrfs/extent_io.c
View file @
5c5aff98
...
...
@@ -4510,8 +4510,7 @@ static int emit_fiemap_extent(struct fiemap_extent_info *fieinfo,
* In this case, the first extent range will be cached but not emitted.
* So we must emit it before ending extent_fiemap().
*/
static
int
emit_last_fiemap_cache
(
struct
btrfs_fs_info
*
fs_info
,
struct
fiemap_extent_info
*
fieinfo
,
static
int
emit_last_fiemap_cache
(
struct
fiemap_extent_info
*
fieinfo
,
struct
fiemap_cache
*
cache
)
{
int
ret
;
...
...
@@ -4718,7 +4717,7 @@ int extent_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
}
out_free:
if
(
!
ret
)
ret
=
emit_last_fiemap_cache
(
root
->
fs_info
,
fieinfo
,
&
cache
);
ret
=
emit_last_fiemap_cache
(
fieinfo
,
&
cache
);
free_extent_map
(
em
);
out:
btrfs_free_path
(
path
);
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment