Re: [PATCH v10 00/22] fs-verity support for XFS with post EOF merkle tree
Andrey Albershteyn <[email protected]> Thu, 28 May 2026 16:25:32 +0200
| Newsgroups | dev.linux.lists.fsverity,net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-btrfs,org.kernel.vger.linux-ext4,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-unionfs,org.kernel.vger.linux-xfs |
|---|---|
| Message-ID | <k2g674gytgm23ef6jfhfikckpnnw4evuobkxxhn2quwgr7dplx@432kdgezw6nu> |
On 2026-05-28 14:20:08, Christian Brauner wrote: > On Tue, May 26, 2026 at 12:19:43PM +0200, Carlos Maiolino wrote: > > On Fri, May 22, 2026 at 02:07:57PM +0200, Christoph Hellwig wrote: > > > On Fri, May 22, 2026 at 12:03:20PM +0200, Christian Brauner wrote: > > > > > I was expecting this to come through xfs tree too if Eric and Christian > > > > > agree. > > > > > > > > You may take it through the xfs tree if there are no conflicts with > > > > vfs-7.2.iomap. If there are I want to add the iomap changes into > > > > vfs-7.2.iomap that you can pull in. > > > > > > Merging the iomap bits through the iomap branch might make sense, given > > > that iomap usually tends to see quite a bit of activity. > > > > > > > That sounds good to me. If you want to go ahead and pull in the iomap > > bits, do so, and give me a heads up when you do it so I'll pull your > > branch locally. > > Great, can the series please be resent based on current vfs-7.2.iomap > then please? Because the iomap changes in this series don't apply > cleanly on vfs-7.2.iomap so we already have merge conflicts... > Sure, I will resend soon. -- - Andrey