The io_tree is passed to several functions that do extent page read/write, but there's a lot of redundancy and things can be simplified. David Sterba (8): btrfs: remove extent_page_data::tree btrfs: drop argument tree from submit_extent_page btrfs: add assertions for tree == inode->io_tree to extent IO helpers btrfs: drop argument tree from btrfs_lock_and_flush_ordered_range btrfs: sink argument tree to extent_read_full_page btrfs: sink argument tree to __extent_read_full_page btrfs: sink arugment tree to contiguous_readpages btrfs: sink argument tree to __do_readpage fs/btrfs/disk-io.c | 4 +--- fs/btrfs/extent_io.c | 50 ++++++++++++++++------------------------- fs/btrfs/extent_io.h | 4 ++-- fs/btrfs/file.c | 2 +- fs/btrfs/inode.c | 6 ++--- fs/btrfs/ordered-data.c | 8 +++---- fs/btrfs/ordered-data.h | 3 +-- 7 files changed, 29 insertions(+), 48 deletions(-) -- 2.25.0
