From: "Darrick J. Wong" <djwong@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [man-pages PATCH RESEND] statx.2: correctly document STATX_ALL
Date: Tue, 5 Jul 2022 15:23:45 -0700 [thread overview]
Message-ID: <YsS58QJf4jQ4r3QM@magnolia> (raw)
In-Reply-To: <20220705183614.16786-1-ebiggers@kernel.org>
On Tue, Jul 05, 2022 at 11:36:14AM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Since kernel commit 581701b7efd6 ("uapi: deprecate STATX_ALL"),
> STATX_ALL is deprecated. It doesn't include STATX_MNT_ID, and it won't
> include any future flags. Update the man page accordingly.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
As the last idiot to trip over this,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> man2/statx.2 | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/man2/statx.2 b/man2/statx.2
> index a8620be6f..561e64f7b 100644
> --- a/man2/statx.2
> +++ b/man2/statx.2
> @@ -244,8 +244,9 @@ STATX_SIZE Want stx_size
> STATX_BLOCKS Want stx_blocks
> STATX_BASIC_STATS [All of the above]
> STATX_BTIME Want stx_btime
> +STATX_ALL The same as STATX_BASIC_STATS | STATX_BTIME.
> + This is deprecated and should not be used.
> STATX_MNT_ID Want stx_mnt_id (since Linux 5.8)
> -STATX_ALL [All currently available fields]
> .TE
> .in
> .PP
>
> base-commit: 88646725187456fad6f17552e96c50c93bd361dc
> --
> 2.37.0
>
next prev parent reply other threads:[~2022-07-05 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 18:36 [man-pages PATCH RESEND] statx.2: correctly document STATX_ALL Eric Biggers
2022-07-05 18:48 ` Andreas Dilger
2022-07-05 22:23 ` Darrick J. Wong [this message]
2022-07-06 23:33 ` 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=YsS58QJf4jQ4r3QM@magnolia \
--to=djwong@kernel.org \
--cc=alx.manpages@gmail.com \
--cc=ebiggers@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).