From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: John Garry <john.g.garry@oracle.com>,
linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org,
djwong@kernel.org, ritesh.list@gmail.com
Subject: Re: [PATCH] statx.2: Update STATX_WRITE_ATOMIC filesystem support
Date: Mon, 16 Dec 2024 13:47:49 +0100 [thread overview]
Message-ID: <20241216124749.nvve7b4q3r2wjud2@devuan> (raw)
In-Reply-To: <20241216123853.g43jqafi7avnntpg@illithid>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Hi Branden, John,
On Mon, Dec 16, 2024 at 06:38:53AM -0600, G. Branden Robinson wrote:
> Hi John,
>
> At 2024-12-16T10:35:42+0000, John Garry wrote:
> > On 05/12/2024 10:02, Alejandro Colomar wrote:
> > > On Thu, Dec 05, 2024 at 09:33:18AM +0000, John Garry wrote:
> > > Nah, we can apply it already. Just let me know if anything changes
> > > before the release.
> >
> > I'd suggest that it is ok to merge this now, but Branden seems to have
> > comments...
>
> I don't generally intend my review comments to be gating, and this is no
> exception. (I should try harder to state that explicitly more often.)
Nah, I just forgot about this patch. Thanks for the ping; I'll apply it
later today (if I don't forget again). :)
Cheers,
Alex
> Please don't delay on my account. :)
>
> Regards,
> Branden
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-16 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 14:53 [PATCH] statx.2: Update STATX_WRITE_ATOMIC filesystem support John Garry
2024-12-04 4:55 ` Darrick J. Wong
2024-12-04 20:45 ` Alejandro Colomar
2024-12-05 9:33 ` John Garry
2024-12-05 10:02 ` Alejandro Colomar
2024-12-05 10:34 ` G. Branden Robinson
2024-12-05 12:02 ` Alejandro Colomar
2024-12-16 10:35 ` John Garry
2024-12-16 12:38 ` G. Branden Robinson
2024-12-16 12:47 ` Alejandro Colomar [this message]
2025-01-04 20:23 ` Alejandro Colomar
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=20241216124749.nvve7b4q3r2wjud2@devuan \
--to=alx@kernel.org \
--cc=djwong@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=john.g.garry@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=ritesh.list@gmail.com \
/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