[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cuyujo64iykwa2axim2jj5fisqnc4xhphasxm5n6nsim5qxvkg@rvtkxg6fj6ni>
Date: Fri, 16 May 2025 15:31:17 +0200
From: Carlos Maiolino <cem@...nel.org>
To: John Garry <john.g.garry@...cle.com>
Cc: Theodore Ts'o <tytso@....edu>,
"Ritesh Harjani (IBM)" <ritesh.list@...il.com>, linux-ext4@...r.kernel.org, Jan Kara <jack@...e.cz>,
djwong@...nel.org, Ojaswin Mujoo <ojaswin@...ux.ibm.com>,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v5 7/7] ext4: Add atomic block write documentation
On Fri, May 16, 2025 at 02:05:05PM +0100, John Garry wrote:
> On 16/05/2025 13:19, Theodore Ts'o wrote:
>
> + Carlos
>
> > On Fri, May 16, 2025 at 09:55:09AM +0100, John Garry wrote:
> >> Or move this file to a common location, and have separate sections for ext4
> >> and xfs? This would save having scattered files for instructions.
> > What is the current outook for the xfs changes landing in the next
> > merge window?
>
> The changes have been queued, please see:
>
> https://lore.kernel.org/linux-xfs/174665351406.2683464.14829425904827876762.stg-ugh@frogsfrogsfrogs/
Hi Ted,
XFS changes are here:
https://web.git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/log/?h=xfs-6.16-merge
>
> > I haven't been tracking the latest rounds of reviews
> > for the xfs atomic writes patchset.
> >
> > If the xfs atomic writes patchset aren't going to land this window,
> > then we can land them as ext4 specific documentation, and when the xfs
> > patches land, we can reorganize the documentation at that point. Does
> > that make sense?
>
They have been also in xfs/for-next for a while now.
This is likely the final state for XFS merge-window and I hope to send it to
Linus as soon as the merge window opens.
Hope this helps.
> So I figure that we can organise the documentation now to cover both
> ext4 and xfs.
>
> Thanks,
> John
Powered by blists - more mailing lists