On 2026-07-02 18:47 -0700, Joanne Koong wrote: > On Thu, Jul 2, 2026 at 9:51 AM Darrick J. Wong <[email protected]> wrote: > > > > On Thu, Jul 02, 2026 at 04:07:05PM +0200, Christoph Hellwig wrote: > > > 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. > > > > I'd say everything but this patch should go in during the merge window > > for 7.3, along with clear instructions to brauner/torvalds to expect > > this patch to appear right before 7.3-rc1 gets tagged, to clean up all > > the other changes that come in. > > Just to clarify, did you mean this patch and the previous one? If i'm > interpreting Christoph's concern correctly, I think he's worried about > other filesystems converting to iomap using the ->iomap_begin() / > ->iomap_end() functions still? That sounds like a good plan to me, for > v3 I'll submit everything but this patch and the last one and then
Ok, so we'll do the prep for vfs-7.3.iomap (aka to be merged in the v7.3-rc1 cycle)... > submit these patches (and any cleanup ones that become necessary) to > Christian right before 7.3-rc1 gets tagged (which as I understand it, > is when the merge window is about to close). and merge these _after_ v7.3-rc1 has been tagged...
