* [PATCH] iomap: remove the unused ifs parameter from ifs_find_dirty_range
@ 2026-08-19 8:48 Pankaj Raghav
2026-08-19 8:58 ` Christoph Hellwig
2026-08-31 8:05 ` Christian Brauner
0 siblings, 2 replies; 3+ messages in thread
From: Pankaj Raghav @ 2026-08-19 8:48 UTC (permalink / raw)
To: Darrick J . Wong, Christian Brauner
Cc: linux-kernel, linux-fsdevel, gost.dev, linux-xfs, pankaj.raghav,
ojaswin, Pankaj Raghav
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.
Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
---
fs/iomap/buffered-io.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
index 0a5ebfda90f1..e11f1327bd98 100644
--- a/fs/iomap/buffered-io.c
+++ b/fs/iomap/buffered-io.c
@@ -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
--
2.51.2
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] iomap: remove the unused ifs parameter from ifs_find_dirty_range
2026-08-19 8:48 [PATCH] iomap: remove the unused ifs parameter from ifs_find_dirty_range Pankaj Raghav
@ 2026-08-19 8:58 ` Christoph Hellwig
2026-08-31 8:05 ` Christian Brauner
1 sibling, 0 replies; 3+ messages in thread
From: Christoph Hellwig @ 2026-08-19 8:58 UTC (permalink / raw)
To: Pankaj Raghav
Cc: Darrick J . Wong, Christian Brauner, linux-kernel, linux-fsdevel,
gost.dev, linux-xfs, pankaj.raghav, ojaswin
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] iomap: remove the unused ifs parameter from ifs_find_dirty_range
2026-08-19 8:48 [PATCH] iomap: remove the unused ifs parameter from ifs_find_dirty_range Pankaj Raghav
2026-08-19 8:58 ` Christoph Hellwig
@ 2026-08-31 8:05 ` Christian Brauner
1 sibling, 0 replies; 3+ messages in thread
From: Christian Brauner @ 2026-08-31 8:05 UTC (permalink / raw)
To: Darrick J . Wong, Pankaj Raghav
Cc: linux-kernel, linux-fsdevel, gost.dev, linux-xfs, pankaj.raghav,
ojaswin
On Wed, 19 Aug 2026 10:48:58 +0200, Pankaj Raghav wrote:
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-08-31 8:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-19 8:48 [PATCH] iomap: remove the unused ifs parameter from ifs_find_dirty_range Pankaj Raghav
2026-08-19 8:58 ` Christoph Hellwig
2026-08-31 8:05 ` Christian Brauner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox