From: Alejandro Colomar <alx@kernel.org>
To: John Garry <john.g.garry@oracle.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] statx.2: Document STATX_SUBVOL
Date: Mon, 25 Nov 2024 11:31:46 +0100 [thread overview]
Message-ID: <20241125103146.pqtapi3h5oizm3j7@devuan> (raw)
In-Reply-To: <aedc8625-a115-47b0-b3ab-1eec9653da42@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]
Hi John,
On Mon, Nov 25, 2024 at 09:03:50AM +0000, John Garry wrote:
> On 24/11/2024 13:35, Alejandro Colomar wrote:
> > Hi Kent, Eric, John,
> >
> > Thread: <https://lore.kernel.org/linux-man/20240311203221.2118219-1-kent.overstreet@linux.dev/T/#u>
> >
> > I revisited this thread today and checked that there wasn't an updated
> > patch. Would you like to send a revised version of the patch?
>
> Hi Alex,
>
> Wasn't this done in the following:
Ahh, true. I cound't find it because it was in another thread. That's
why I prefer that patch v2 is a reply to the same thread that sent patch
v1. :-) I'll have to document this in the CONTRIBUTING.d/* guidelines.
Thanks!
>
> commit d0621648b4b5a356e86cea23e842f2591461f0cf
> Author: Kent Overstreet <kent.overstreet@linux.dev>
> Date: Thu Jun 20 13:00:17 2024 +0000
>
> statx.2: Document STATX_SUBVOL
>
> Document the new statx.stx_subvol field.
>
> This would be clearer if we had a proper API for walking subvolumes that
> we could refer to, but that's still coming.
>
> Link: https://urldefense.com/v3/__https://lore.kernel.org/linux-fsdevel/20240308022914.196982-1-kent.overstreet@linux.dev/__;!!ACWV5N9M2RV99hQ!JYMR3Qwb11MmwlhEqgGhq3ITse9gIJ2sfyZQHyiVMQsb77VfyLGvmdLonkpcrGymbqfkUZE0DnYahWZPrc-vZG1rkIHW$
>
> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
> [jpg: mention supported FSes and formatting improvements]
> Signed-off-by: John Garry <john.g.garry@oracle.com>
> Cc: Eric Biggers <ebiggers@kernel.org>
> Cc: <linux-fsdevel@vger.kernel.org>
> Message-ID: <20240620130017.2686511-1-john.g.garry@oracle.com>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
>
> BTW, on another totally separate topic, there is nothing for this:
>
> https://lore.kernel.org/linux-fsdevel/f20a786f-156a-4772-8633-66518bd09a02@oracle.com/
>
> right?
grep(1) seems to say you're right.
alx@devuan:~/src/linux/man-pages/man-pages/contrib$ grep -rn RWF_NOAPPEND
alx@devuan:~/src/linux/man-pages/man-pages/contrib$
I guess we should ping that thread.
Have a lovely day!
Alex
>
> Thanks,
> John
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-11-25 10:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 20:31 [PATCH] statx.2: Document STATX_SUBVOL Kent Overstreet
2024-03-12 2:19 ` Eric Biggers
2024-03-15 13:47 ` Alejandro Colomar
2024-06-17 7:36 ` John Garry
2024-06-17 8:47 ` Alejandro Colomar
2024-06-18 9:19 ` John Garry
2024-06-18 12:14 ` Alejandro Colomar
2024-11-24 13:35 ` Alejandro Colomar
2024-11-25 9:03 ` John Garry
2024-11-25 10:31 ` Alejandro Colomar [this message]
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=20241125103146.pqtapi3h5oizm3j7@devuan \
--to=alx@kernel.org \
--cc=ebiggers@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.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