From: "Darrick J. Wong" <djwong@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
John Garry <john.g.garry@oracle.com>,
Catherine Hoang <catherine.hoang@oracle.com>,
linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@infradead.org>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>,
linux-block@vger.kernel.org, Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [ANNOUNCE v2] work tree for untorn filesystem writes
Date: Wed, 6 Nov 2024 08:15:41 -0800 [thread overview]
Message-ID: <20241106161541.GN2386201@frogsfrogsfrogs> (raw)
In-Reply-To: <20241106-zerkleinern-verzweifeln-7ec8173c56ad@brauner>
On Wed, Nov 06, 2024 at 10:50:21AM +0100, Christian Brauner wrote:
> On Tue, Nov 05, 2024 at 04:57:40PM -0800, Darrick J. Wong wrote:
> > Hi everyone,
> >
> > Here's a slightly updated working branch for the filesystem side of
> > atomic write changes for 6.13:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=fs-atomic_2024-11-05
> >
> > This branch is, like yesterday's, based off of axboe's
> > for-6.13/block-atomic branch:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/log/?h=for-6.13/block-atomic
> >
> > The only difference is that I added Ojaswin's Tested-by: tags to the end
> > of the xfs series. I have done basic testing with the shell script at
> > the end of this email and am satisfied that it at least seems to do the
> > (limited) things that I think we're targeting for 6.13.
> >
> > Christian: Could you pull this fs-atomic branch into your vfs.git work
> > for 6.13, please?
>
> Of course!
>
> I did git pull fs-atomic_2024-11-05 from your tree. It should show up in
> -next tomorrow.
Yay, thank you!!
--D
next prev parent reply other threads:[~2024-11-06 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 0:57 [ANNOUNCE v2] work tree for untorn filesystem writes Darrick J. Wong
2024-11-06 9:50 ` Christian Brauner
2024-11-06 16:15 ` Darrick J. Wong [this message]
2024-11-07 13:49 ` Carlos Maiolino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241106161541.GN2386201@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=catherine.hoang@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox