On Tue, Sep 10, 2019 at 12:01:24AM -0700, Christoph Hellwig wrote: > On Mon, Sep 02, 2019 at 10:16:37AM -0700, Christoph Hellwig wrote: > > On Sun, Sep 01, 2019 at 01:44:00PM -0700, Darrick J. Wong wrote: > > > Would you mind rebasing the remaining patches against iomap-for-next and > > > sending that out? I'll try to get to it before I go on vacation 6 - 15 > > > Sept. > > > > Ok. Testing right now, but the rebase was trivial. > > > > > Admittedly I think the controversial questions are still "How much > > > writeback code are we outsourcing to iomap anyway?" and "Do we want to > > > do the added stress of keeping that going without breaking everyone > > > else"? IOWs, more philosophical than just the mechanics of porting code > > > around. > > > > At least as far as I'm concerned the more code that is common the > > better so that I don't have to fix up 4 badly maintained half-assed > > forks of the same code (hello mpage, ext4 and f2fs..). > > Any news? Darrick is still on holidays. The iomap-for-next branch has this series in it already(*), but I suspect at this point the XFS conversion is going to have to wait until the next cycle. Cheers, Dave. (*) https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/log/?h=iomap-for-next -- Dave Chinner david@xxxxxxxxxxxxx
