From: Pankaj Raghav <p.raghav@samsung.com>
To: "Darrick J . Wong" <djwong@kernel.org>,
Christian Brauner <brauner@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
gost.dev@samsung.com, linux-xfs@vger.kernel.org,
pankaj.raghav@linux.dev, ojaswin@linux.ibm.com,
Pankaj Raghav <p.raghav@samsung.com>
Subject: [PATCH] iomap: remove the unused ifs parameter from ifs_find_dirty_range
Date: Wed, 19 Aug 2026 10:48:58 +0200 [thread overview]
Message-ID: <20260819084858.778285-1-p.raghav@samsung.com> (raw)
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
next reply other threads:[~2026-08-19 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 8:48 Pankaj Raghav [this message]
2026-08-19 8:58 ` [PATCH] iomap: remove the unused ifs parameter from ifs_find_dirty_range Christoph Hellwig
2026-08-31 8:05 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260819084858.778285-1-p.raghav@samsung.com \
--to=p.raghav@samsung.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=gost.dev@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=pankaj.raghav@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.