From: John Garry <john.g.garry@oracle.com>
To: Carlos Maiolino <cem@kernel.org>
Cc: djwong@kernel.org, hch@lst.de, dan.j.williams@intel.com,
willy@infradead.org, jack@suse.cz, brauner@kernel.org,
viro@zeniv.linux.org.uk, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] xfs and DAX atomic writes changes
Date: Mon, 11 Aug 2025 13:08:59 +0100 [thread overview]
Message-ID: <a1b9477e-0783-478d-9c64-8522f8554a35@oracle.com> (raw)
In-Reply-To: <rnils56yqukku5j5t22ac5zru7esi35beo25nhz2ybhxqks5nf@u2xt7j4biinr>
On 11/08/2025 13:06, Carlos Maiolino wrote:
>> I was expecting you to pick these up.
> I did, for -rc1.
>
>> Shall I resend next week after v6.17-rc1 is released?
> No, I already have them queued up for -rc1, no need to send them again
Great, thanks. I was just prepping to send again :)
next prev parent reply other threads:[~2025-08-11 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 8:12 [PATCH v3 0/3] xfs and DAX atomic writes changes John Garry
2025-07-24 8:12 ` [PATCH v3 1/3] fs/dax: Reject IOCB_ATOMIC in dax_iomap_rw() John Garry
2025-07-24 16:25 ` Darrick J. Wong
2025-07-24 8:12 ` [PATCH v3 2/3] xfs: disallow atomic writes on DAX John Garry
2025-07-24 8:12 ` [PATCH v3 3/3] xfs: reject max_atomic_write mount option for no reflink John Garry
2025-07-24 16:32 ` Darrick J. Wong
2025-07-25 8:39 ` John Garry
2025-07-25 15:49 ` Darrick J. Wong
2025-08-06 9:15 ` [PATCH v3 0/3] xfs and DAX atomic writes changes John Garry
2025-08-11 12:06 ` Carlos Maiolino
2025-08-11 12:08 ` John Garry [this message]
2025-08-11 12:13 ` Carlos Maiolino
2025-08-12 7:33 ` 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=a1b9477e-0783-478d-9c64-8522f8554a35@oracle.com \
--to=john.g.garry@oracle.com \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).