From: Alejandro Colomar <alx@kernel.org>
To: Guillem Jover <guillem@hadrons.org>,
linux-man@vger.kernel.org, Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH 1/2] process_madvise.2: Document the glibc wrapper
Date: Wed, 28 Feb 2024 00:14:36 +0100 [thread overview]
Message-ID: <Zd5s3K5sI9012d-I@debian> (raw)
In-Reply-To: <Zd5fMGvIlmhQyONs@thunder.hadrons.org>
[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]
Hi!
On Tue, Feb 27, 2024 at 11:16:16PM +0100, Guillem Jover wrote:
> Hi!
>
> On Sun, 2024-02-25 at 13:23:22 +0100, Alejandro Colomar wrote:
> > diff --git a/man2/process_madvise.2 b/man2/process_madvise.2
> > index 53fd57598..ed8739663 100644
> > --- a/man2/process_madvise.2
> > +++ b/man2/process_madvise.2
> > @@ -187,6 +176,7 @@ .SH STANDARDS
> > Linux.
> > .SH HISTORY
> > Linux 5.10.
> > +glibc 2.36.
> > .\" commit ecb8ac8b1f146915aa6b96449b66dd48984caacc
>
> This commit id seems to belong to Linux, so perhaps keep it after the
> Linux version reference?
Yup! Thanks. Since I already pushed that to master, I've written a
fix. I'll push it tomorrow, if it looks good to you.
Havea lovely night!
Alex
---
commit 22c0efa9a291c666c0b44a74b9a7ff4a04a7f674 (HEAD -> contrib)
Author: Alejandro Colomar <alx@kernel.org>
Date: Wed Feb 28 00:10:23 2024 +0100
process_madvise.2: Fix comments about commit ids
Move the comment about the Linux commit id, specify that it's a Linux
commit, and add the glibc commit id too.
Link: <https://sourceware.org/bugzilla/show_bug.cgi?id=27380>
Link: <https://lore.kernel.org/linux-man/Zd5fMGvIlmhQyONs@thunder.hadrons.org/T/#m9129640e1293a94ff1606a2f973522f40c968306>
Reported-by: Guillem Jover <guillem@hadrons.org>
Cc: Florian Weimer <fweimer@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
diff --git a/man2/process_madvise.2 b/man2/process_madvise.2
index 2d91924ca..2c9f0b3f9 100644
--- a/man2/process_madvise.2
+++ b/man2/process_madvise.2
@@ -176,8 +176,9 @@ .SH STANDARDS
Linux.
.SH HISTORY
Linux 5.10.
+.\" Linux commit ecb8ac8b1f146915aa6b96449b66dd48984caacc
glibc 2.36.
-.\" commit ecb8ac8b1f146915aa6b96449b66dd48984caacc
+.\" glibc commit d19ee3473d68ca0e794f3a8b7677a0983ae1342e
.P
Support for this system call is optional,
depending on the setting of the
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-02-27 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 12:23 [PATCH 1/2] process_madvise.2: Document the glibc wrapper Alejandro Colomar
2024-02-25 12:23 ` [PATCH 2/2] process_madvise.2: Rename parameter, and use array syntax Alejandro Colomar
2024-02-27 22:16 ` [PATCH 1/2] process_madvise.2: Document the glibc wrapper Guillem Jover
2024-02-27 23:14 ` 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=Zd5s3K5sI9012d-I@debian \
--to=alx@kernel.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=guillem@hadrons.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 read-only IMAP folder(s) and NNTP newsgroup(s).