btrfs: sink unlock_extent parameter gfp_flags

Browse source

All callers pass either GFP_NOFS or GFP_KERNEL now, so we can sink the
parameter to the function, though we lose some of the slightly better
semantics of GFP_KERNEL in some places, it's worth cleaning up the
callchains.

Signed-off-by: David Sterba <dsterba@suse.com>

...

This commit is contained in:

David Sterba 2017-12-12 21:43:52 +01:00

parent d810a4be1a

commit e43bbe5e16

8 changed files with 32 additions and 40 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

fs/btrfs/disk-io.c

View file

10

fs/btrfs/extent_io.c

View file

4

fs/btrfs/extent_io.h

View file

15

fs/btrfs/file.c

View file

5

fs/btrfs/free-space-cache.c

View file

26

fs/btrfs/inode.c

View file

7

fs/btrfs/ioctl.c

View file

3

fs/btrfs/scrub.c

View file