iomap: remove the unused ifs parameter from ifs_find_dirty_range
Subsystems (2)
PATCH 1/1 iomap: remove the unused ifs parameter from ifs_find_dirty_range
commit fed9c62d28b7 ("iomap: use find_next_bit() for dirty bitmap scanning") removed the use of ifs in ifs_find_dirty_range(). Remove the unused parameter.
--- fs/iomap/buffered-io.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
fs/iomap/buffered-io.c +3 -3
@@ -143,8 +143,8 @@ static unsigned ifs_next_clean_block(struct folio *folio, blks + start_blk) - blks; } -static unsigned ifs_find_dirty_range (struct folio *folio, -struct iomap_folio_state *ifs,u64 *range_start,u64 range_end) +static unsigned ifs_find_dirty_range (struct folio *folio,u64 *range_start, +u64 range_end) {struct inode *inode = folio->mapping->host; unsigned start_blk =
@@ -176,7 +176,7 @@ static unsigned iomap_find_dirty_range(struct folio *folio, u64 *range_start,return 0 ;if (ifs) -return ifs_find_dirty_range (folio, ifs, range_start, range_end); +return ifs_find_dirty_range (folio, range_start, range_end);return range_end - *range_start; }
base-commit: 352cda83346d4c35113b056486d2358da6343737
Signature · 1 line
2.51.2
Looks good:
Quoted 1 line · Pankaj Raghav
iomap: remove the unused ifs parameter from
ifs_find_dirty_range
Applied to the vfs-7.4.iomap branch of the vfs/vfs.git tree. Patches in the vfs-7.4.iomap branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase, trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git branch: vfs-7.4.iomap
[1/1] iomap: remove the unused ifs parameter from ifs_find_dirty_range
https://git.kernel.org/vfs/vfs/c/1aea0c4a34c7