From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>
Subject: Re: ptrace.2: Simplify signature? s/enum \w*/int/
Date: Wed, 10 Feb 2021 22:31:03 +0100 [thread overview]
Message-ID: <1ac680f8-e61b-440a-4c51-b34842d229c3@gmail.com> (raw)
In-Reply-To: <e49ab35b-a131-1adf-4b5c-5285e662d26c@gmail.com>
Hi Alex,
On 2/10/21 11:18 AM, Alejandro Colomar (man-pages) wrote:
> On 2/9/21 11:34 PM, Alejandro Colomar (man-pages) wrote:
> [...]
>>
>> Here are the glibc results (grepping though the kernel is taking much
>> longer, but I guess the command will have ended by tomorrow morning, and
>> I'll send you a follow-up.
>
> There aren't syscalls using enum (as expected).
>
> .../linux/linux$ func_list ../man-pages/man2 \
> |while read -r f; do
> grep_syscall $f;
> done \
> |grep enum;
> .../linux/linux$
Okay -- I defer to your judgement. You send me a patch,
and I'll apply it.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2021-02-10 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e7685576-db7b-f53d-26b9-64ee6621aea1@gmail.com>
2021-02-08 22:36 ` ptrace.2: Simplify signature? s/enum \w*/int/ Alejandro Colomar (man-pages)
2021-02-09 18:25 ` Michael Kerrisk (man-pages)
2021-02-09 22:34 ` Alejandro Colomar (man-pages)
2021-02-10 10:18 ` Alejandro Colomar (man-pages)
2021-02-10 10:20 ` Alejandro Colomar (man-pages)
2021-02-10 21:31 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <CAHBesv0hwHLJMzqBq+e4LpDAWV98H4+d5mv4gSbFFWs8oV7b3w@mail.gmail.com>
[not found] ` <20d93fb1-766e-ddf8-a7d8-b00f7bd04cc6@gmail.com>
2021-02-11 17:28 ` Alejandro Colomar (man-pages)
2021-02-13 10:16 ` Alejandro Colomar (man-pages)
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=1ac680f8-e61b-440a-4c51-b34842d229c3@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--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