From: Alejandro Colomar <alx@kernel.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: linux-man@vger.kernel.org, Suren Baghdasaryan <surenb@google.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
linux-mm@kvack.org
Subject: Re: [PATCH man-pages v2] process_madvise.2: describe 6.13 behaviour permitting all madvise flags
Date: Wed, 4 Dec 2024 11:13:44 +0100 [thread overview]
Message-ID: <20241204101344.ont4gjc3ewltiec6@devuan> (raw)
In-Reply-To: <20241129164422.89837-1-lorenzo.stoakes@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]
Hi Lorenzo, David,
On Fri, Nov 29, 2024 at 04:44:22PM +0000, Lorenzo Stoakes wrote:
> Since Linux 6.13 it has become possible to use all madvise flags when targeting
> the calling process. Update the man page to reflect this change.
>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Thanks for the patch and the review! I've applied it, with minor
tweaks.
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=7148a8cca8d693731d98c09bb7bf9d585a36e695>
> ---
>
> v2:
> * Use semantic newlines as suggested by Alejandro.
> v1:
> https://lore.kernel.org/all/20241129095507.11001-1-lorenzo.stoakes@oracle.com/
>
> man/man2/process_madvise.2 | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/man/man2/process_madvise.2 b/man/man2/process_madvise.2
> index b78a61553..2ebbfea44 100644
> --- a/man/man2/process_madvise.2
> +++ b/man/man2/process_madvise.2
> @@ -54,7 +54,9 @@ This value must be less than or equal to
> or accessible via the call
> .IR sysconf(_SC_IOV_MAX) ).
> .P
> -The
> +If manipulating another process,
> +or before Linux 6.13,
> +the
> .I advice
> argument is one of the following values:
> .TP
> @@ -74,6 +76,10 @@ See
> See
> .BR madvise (2).
> .P
> +Starting in Linux 6.13,
We use consistently "Since Linux ..." for saying this. That allows
grepping for a consistent phrase. I've applied a fix for all pages that
still had this old wording:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=b159e0d6770a860f0d0ae1693dddb3b6116e7d9b>
Have a lovely day!
Alex
> +when manipulating the calling process,
> +any advice flag is permitted.
> +.P
> The
> .I flags
> argument is reserved for future use; currently, this argument must be
> --
> 2.47.1
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-04 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 16:44 Lorenzo Stoakes
2024-12-04 10:13 ` Alejandro Colomar [this message]
2024-12-04 11:43 ` Lorenzo Stoakes
2024-12-05 17:41 ` Vlastimil Babka
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=20241204101344.ont4gjc3ewltiec6@devuan \
--to=alx@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=jannh@google.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--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