Re: [PATCH v2 17/18] iomap: pass iomap_next_fn directly instead of struct iomap_ops
Christoph Hellwig <[email protected]> Thu, 2 Jul 2026 16:07:05 +0200
| Newsgroups | dev.linux.lists.gfs2,dev.linux.lists.fuse-devel,dev.linux.lists.ntfs3,dev.linux.lists.nvdimm,net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-block,org.kernel.vger.linux-btrfs,org.kernel.vger.linux-ext4,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-xfs,org.ozlabs.lists.linux-erofs |
|---|---|
| Message-ID | <[email protected]> |
Looks good: Reviewed-by: Christoph Hellwig <[email protected]> In terms of merge logistics, I wonder if we should delay this and the previous patch to the next merge window so that we can minimize the cross-subsystem merge pain with more file system iomap conversion. If none of them actually happen until rc6 or so, orif the merges aren't painful we could still pick them up late in the merge window.