From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Alejandro Colomar <alx@kernel.org>
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] process_madvise.2: describe 6.13 behaviour permitting all madvise flags
Date: Fri, 29 Nov 2024 14:38:01 +0000 [thread overview]
Message-ID: <c5c781c6-765c-4ba0-b145-b5f7a6b46e46@lucifer.local> (raw)
In-Reply-To: <20241129123741.n7qxysu3w3ulurj7@devuan>
On Fri, Nov 29, 2024 at 01:37:41PM +0100, Alejandro Colomar wrote:
> Hi Lorenzo,
>
> On Fri, Nov 29, 2024 at 09:55:07AM +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.
> >
> > Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > ---
> > man/man2/process_madvise.2 | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/man/man2/process_madvise.2 b/man/man2/process_madvise.2
> > index b78a61553..d12407bdb 100644
> > --- a/man/man2/process_madvise.2
> > +++ b/man/man2/process_madvise.2
> > @@ -54,7 +54,7 @@ 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 prior to Linux 6.13, the
>
> For consistency with other pages, how s/prior to/before/? Prior to is
> ok; it's just for being able to grep for a single expression.
Ah, I think I saw a 'prior to' somewhere but actually no, that was the 'starting
in' below, my mistake.
Will fix up!
>
> > .I advice
> > argument is one of the following values:
> > .TP
> > @@ -74,6 +74,9 @@ See
> > See
> > .BR madvise (2).
> > .P
> > +Starting in Linux 6.13, when manipulating the calling process, any advice flag
> > +is permitted.
>
> Please use semantic newlines. See man-pages(7), and the other email.
Ack, will do!
>
> Cheers,
> Alex
>
> > +.P
> > The
> > .I flags
> > argument is reserved for future use; currently, this argument must be
> > --
> > 2.47.1
>
> --
> <https://www.alejandro-colomar.es/>
Will respin and send a v2 shortly. Thanks!
prev parent reply other threads:[~2024-11-29 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 9:55 Lorenzo Stoakes
2024-11-29 12:14 ` David Hildenbrand
2024-11-29 12:16 ` Lorenzo Stoakes
2024-11-29 12:37 ` Alejandro Colomar
2024-11-29 14:38 ` Lorenzo Stoakes [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=c5c781c6-765c-4ba0-b145-b5f7a6b46e46@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=alx@kernel.org \
--cc=jannh@google.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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