From: enh <enh@google.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Stefan Puiu <stefan.puiu@gmail.com>,
Bruno Haible <bruno@clisp.org>,
linux-man@vger.kernel.org,
GNU C Library <libc-alpha@sourceware.org>,
linux-api@vger.kernel.org
Subject: Re: [PATCH 1/2] man*/: epoll_*(), fcntl(), flock(), ioctl(), msgctl(), *prctl(), ptrace(), quotactl(), reboot(), semctl(), shmctl(), lockf(): Consistently use 'op' and 'operation'
Date: Tue, 5 Mar 2024 11:19:09 -0800 [thread overview]
Message-ID: <CAJgzZoofRZxmOnaQyi_+e1eZnZvKp_iz5j294Bp-H+GwJhSA=g@mail.gmail.com> (raw)
In-Reply-To: <ZedgnagXMV5aTcsM@debian>
On Tue, Mar 5, 2024 at 10:12 AM Alejandro Colomar <alx@kernel.org> wrote:
>
> On Sun, Mar 03, 2024 at 01:15:09PM +0100, Alejandro Colomar wrote:
> > Reported-by: Bruno Haible <bruno@clisp.org>
> > Cc: Elliott Hughes <enh@google.com>
> > Cc: Stefan Puiu <stefan.puiu@gmail.com>
> > Signed-off-by: Alejandro Colomar <alx@kernel.org>
> > ---
> > man2/arch_prctl.2 | 12 +++---
> > man2/epoll_wait.2 | 4 +-
> > man2/fcntl.2 | 70 +++++++++++++++----------------
> > man2/flock.2 | 6 +--
> > man2/ioctl.2 | 30 +++++++-------
> > man2/ioctl_console.2 | 8 ++--
> > man2/ioctl_fideduperange.2 | 2 +-
> > man2/ioctl_getfsmap.2 | 6 +--
> > man2/ioctl_ns.2 | 2 +-
> > man2/ioctl_tty.2 | 10 ++---
> > man2/ioctl_userfaultfd.2 | 10 ++---
> > man2/msgctl.2 | 16 ++++----
> > man2/prctl.2 | 84 +++++++++++++++++++-------------------
> > man2/ptrace.2 | 60 +++++++++++++--------------
> > man2/quotactl.2 | 34 +++++++--------
> > man2/reboot.2 | 19 +++++----
> > man2/semctl.2 | 22 +++++-----
> > man2/shmctl.2 | 20 +++++----
> > man3/lockf.3 | 11 ++---
> > 19 files changed, 217 insertions(+), 209 deletions(-)
> >
> > diff --git a/man2/arch_prctl.2 b/man2/arch_prctl.2
> > index bbb85866c..680d36395 100644
> > --- a/man2/arch_prctl.2
> > +++ b/man2/arch_prctl.2
> > @@ -14,8 +14,8 @@ .SH SYNOPSIS
> > .BR "#include <sys/syscall.h>" " /* Definition of " SYS_* " constants */"
> > .B #include <unistd.h>
> > .P
> > -.BI "int syscall(SYS_arch_prctl, int " code ", unsigned long " addr );
> > -.BI "int syscall(SYS_arch_prctl, int " code ", unsigned long *" addr );
> > +.BI "int syscall(SYS_arch_prctl, int " op ", unsigned long " addr );
> > +.BI "int syscall(SYS_arch_prctl, int " op ", unsigned long *" addr );
>
> [...]
>
> Hi Elliott!
>
> This is already in master. Feel free to do a similar thing in bionic.
> ;)
already did :-)
https://android-review.googlesource.com/c/platform/bionic/+/2987969
> Have a lovely day!
> Alex
>
> --
> <https://www.alejandro-colomar.es/>
> Looking for a remote C programming job at the moment.
next prev parent reply other threads:[~2024-03-05 19:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 20:51 [PATCH] prctl.2: Fix typo Bruno Haible
2023-10-31 12:40 ` Alejandro Colomar
2023-10-31 14:31 ` Stefan Puiu
2023-10-31 16:11 ` Alejandro Colomar
2023-10-31 16:19 ` enh
2023-10-31 18:40 ` Alejandro Colomar
2023-10-31 19:15 ` enh
2023-10-31 21:23 ` Alejandro Colomar
2023-11-01 0:37 ` enh
2023-11-01 10:16 ` Alejandro Colomar
2024-03-03 12:15 ` [PATCH 0/2] Use terms consistently in function parameter names Alejandro Colomar
2024-03-03 12:15 ` [PATCH 1/2] man*/: epoll_*(), fcntl(), flock(), ioctl(), msgctl(), *prctl(), ptrace(), quotactl(), reboot(), semctl(), shmctl(), lockf(): Consistently use 'op' and 'operation' Alejandro Colomar
2024-03-05 18:12 ` Alejandro Colomar
2024-03-05 19:19 ` enh [this message]
2024-03-03 12:15 ` [PATCH 2/2] clock_nanosleep.2, nanosleep.2: Use 'duration' rather than 'request' Alejandro Colomar
2024-03-03 12:45 ` Bruno Haible
2024-03-03 12:55 ` Alejandro Colomar
2024-03-03 13:02 ` [PATCH v2 2/2] " Alejandro Colomar
2024-03-05 0:18 ` [PATCH 2/2] clock_nanosleep.2, " enh
2024-03-05 0:34 ` Alejandro Colomar
2024-03-05 0:56 ` enh
2024-03-05 1:11 ` Alejandro Colomar
2024-03-05 1:26 ` [PATCH v3 3/3] clock_nanosleep.2: Use 't' " Alejandro Colomar
2024-03-05 22:22 ` [PATCH 2/2] clock_nanosleep.2, nanosleep.2: Use 'duration' " enh
2023-10-31 17:08 ` [PATCH] prctl.2: Fix typo Bruno Haible
2023-10-31 21:20 ` 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='CAJgzZoofRZxmOnaQyi_+e1eZnZvKp_iz5j294Bp-H+GwJhSA=g@mail.gmail.com' \
--to=enh@google.com \
--cc=alx@kernel.org \
--cc=bruno@clisp.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=stefan.puiu@gmail.com \
/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).