From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: Willem de Bruijn <willemb@google.com>,
linux-man <linux-man@vger.kernel.org>,
Florian Weimer <fweimer@redhat.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-api@vger.kernel.org
Subject: Re: epoll_wait.2: epoll_pwait2(2) prototype
Date: Sat, 13 Mar 2021 18:10:04 +0100 [thread overview]
Message-ID: <db9dbcc6-91e0-bfc3-0f19-b91fd2afec24@gmail.com> (raw)
In-Reply-To: <20210313170250.GA15968@altlinux.org>
Hi Dmitry,
On 3/13/21 6:02 PM, Dmitry V. Levin wrote:
> Hi Alex,
>
> On Sat, Mar 13, 2021 at 05:48:08PM +0100, Alejandro Colomar (man-pages) wrote:
>> Hi Willem,
>>
>> I checked that the prototype of the kernel epoll_pwait2() syscall is
>> different from the one we recently merged; it has one more parameter
>> 'size_t sigsetsize':
[...]
>>
>> I'm could fix the prototype, but maybe there are more changes needed for
>> the manual page.
>>
>> Would you mind fixing it?
>
> Looks like the 6th argument of epoll_pwait and epoll_pwait2 syscalls
> is already described in "C library/kernel differences" subsection of
> epoll_pwait2(2).
Ahhh, I didn't see it, ok. That's in BUGS by mistake. I'll move it to
NOTES, where it should be.
Thanks,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
prev parent reply other threads:[~2021-03-13 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 16:48 epoll_wait.2: epoll_pwait2(2) prototype Alejandro Colomar (man-pages)
2021-03-13 17:02 ` Dmitry V. Levin
2021-03-13 17:10 ` Alejandro Colomar (man-pages) [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=db9dbcc6-91e0-bfc3-0f19-b91fd2afec24@gmail.com \
--to=alx.manpages@gmail.com \
--cc=fweimer@redhat.com \
--cc=ldv@altlinux.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=willemb@google.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 NNTP newsgroup(s).