All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joanne Koong <joannelkoong@gmail.com>
To: Christian Brauner <brauner@kernel.org>,
	hch@lst.de, "Darrick J . Wong" <djwong@kernel.org>,
	linux-fsdevel@vger.kernel.org
Cc: changfengnan@bytedance.com, kbusch@kernel.org,
	Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
	Jonathan Corbet <corbet@lwn.net>, David Sterba <dsterba@suse.com>,
	Gao Xiang <xiang@kernel.org>, Namjae Jeon <linkinjeon@kernel.org>,
	Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Andreas Gruenbacher <agruenba@redhat.com>,
	Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>,
	Hyunchul Lee <hyc.lee@gmail.com>,
	Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
	Carlos Maiolino <cem@kernel.org>,
	Damien Le Moal <dlemoal@kernel.org>,
	libaokun@linux.alibaba.com, bfoster@redhat.com,
	linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: [PATCH v5 19/22] exfat: convert iomap ops to ->iomap_next()
Date: Wed, 29 Jul 2026 12:27:34 -0700	[thread overview]
Message-ID: <20260729192737.3190206-20-joannelkoong@gmail.com> (raw)
In-Reply-To: <20260729192737.3190206-1-joannelkoong@gmail.com>

Convert exfat iomap_ops to the new ->iomap_next() callback. Each
callback is generated with the DEFINE_IOMAP_ITER_NEXT() and
DEFINE_IOMAP_ITER_NEXT_END() macros, which wrap the iomap_iter_next()
helper to finish the previous mapping if needed and produce the next
one. No functional changes are intended.

Acked-by: Namjae Jeon <linkinjeon@kernel.org>
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
---
 fs/exfat/iomap.c | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/fs/exfat/iomap.c b/fs/exfat/iomap.c
index 1aac38e63fe6..b6dd396aa60a 100644
--- a/fs/exfat/iomap.c
+++ b/fs/exfat/iomap.c
@@ -151,8 +151,10 @@ static int exfat_write_iomap_begin(struct inode *inode, loff_t offset, loff_t le
 	return __exfat_iomap_begin(inode, offset, length, flags, iomap, true);
 }
 
+static DEFINE_IOMAP_ITER_NEXT(exfat_iomap_next, exfat_iomap_begin);
+
 const struct iomap_ops exfat_iomap_ops = {
-	.iomap_begin = exfat_iomap_begin,
+	.iomap_next = exfat_iomap_next,
 };
 
 /*
@@ -186,9 +188,11 @@ static int exfat_write_iomap_end(struct inode *inode, loff_t pos, loff_t length,
 	return written;
 }
 
+static DEFINE_IOMAP_ITER_NEXT_END(exfat_write_iomap_next,
+		exfat_write_iomap_begin, exfat_write_iomap_end);
+
 const struct iomap_ops exfat_write_iomap_ops = {
-	.iomap_begin	= exfat_write_iomap_begin,
-	.iomap_end	= exfat_write_iomap_end,
+	.iomap_next	= exfat_write_iomap_next,
 };
 
 /*
-- 
2.52.0


  parent reply	other threads:[~2026-07-29 19:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 19:27 [PATCH v5 00/22] iomap: convert to in-iter iomap_next() model Joanne Koong
2026-07-29 19:27 ` [PATCH v5 01/22] iomap: release the folio batch on iomap callback failures Joanne Koong
2026-07-29 20:53   ` Darrick J. Wong
2026-07-30  7:29   ` Christoph Hellwig
2026-07-29 19:27 ` [PATCH v5 02/22] iomap: split iomap_iter() logic into iomap_iter_next() Joanne Koong
2026-07-29 19:27 ` [PATCH v5 03/22] iomap: decouple simple direct I/O reads from iomap_dio_rw Joanne Koong
2026-07-29 19:27 ` [PATCH v5 04/22] iomap: use GFP_NOWAIT when application for iomap_dio_simple allocations Joanne Koong
2026-07-29 19:27 ` [PATCH v5 05/22] iomap: add ->iomap_next() Joanne Koong
2026-07-29 19:27 ` [PATCH v5 06/22] xfs: convert iomap ops to ->iomap_next() Joanne Koong
2026-07-29 19:27 ` [PATCH v5 07/22] btrfs: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 08/22] ntfs3: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 09/22] ntfs: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 10/22] ext4: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 11/22] erofs: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 12/22] zonefs: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 13/22] ext2: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 14/22] block: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 15/22] f2fs: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 16/22] gfs2: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 17/22] hpfs: " Joanne Koong
2026-07-29 19:27 ` [PATCH v5 18/22] fuse: " Joanne Koong
2026-07-29 19:27 ` Joanne Koong [this message]
2026-07-29 19:27 ` [PATCH v5 20/22] iomap: remove ->iomap_begin()/->iomap_end() legacy path Joanne Koong
2026-07-29 19:27 ` [PATCH v5 21/22] iomap: pass iomap_iter_next_fn directly instead of struct iomap_ops Joanne Koong
2026-07-29 19:27 ` [PATCH v5 22/22] Documentation: iomap: update docs to reflect iomap_iter_next model Joanne Koong
2026-07-30 10:33 ` (subset) [PATCH v5 00/22] iomap: convert to in-iter iomap_next() model Christian Brauner
2026-07-31 13:40   ` 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=20260729192737.3190206-20-joannelkoong@gmail.com \
    --to=joannelkoong@gmail.com \
    --cc=agruenba@redhat.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=bfoster@redhat.com \
    --cc=brauner@kernel.org \
    --cc=cem@kernel.org \
    --cc=changfengnan@bytedance.com \
    --cc=corbet@lwn.net \
    --cc=djwong@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=dsterba@suse.com \
    --cc=hch@lst.de \
    --cc=hyc.lee@gmail.com \
    --cc=jack@suse.cz \
    --cc=jaegeuk@kernel.org \
    --cc=kbusch@kernel.org \
    --cc=libaokun@linux.alibaba.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mikulas@artax.karlin.mff.cuni.cz \
    --cc=tytso@mit.edu \
    --cc=willy@infradead.org \
    --cc=xiang@kernel.org \
    /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.