From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: mtk.manpages@gmail.com
Cc: nd@arm.com, linux-man@vger.kernel.org,
GNU C Library <libc-alpha@sourceware.org>,
Rich Felker <dalias@libc.org>
Subject: glibc and linux-man disagrees about pkey_alloc
Date: Wed, 16 May 2018 12:10:40 +0100 [thread overview]
Message-ID: <adae131e-c782-9508-808f-9cbea92ef694@arm.com> (raw)
glibc sysdeps/unix/sysv/linux/bits/mman-shared.h:
int pkey_alloc (unsigned int __flags, unsigned int __access_rights) __THROW;
linux-man http://man7.org/linux/man-pages/man2/pkey_alloc.2.html :
int pkey_alloc(unsigned long flags, unsigned long access_rights);
i assume the documentation should be fixed (as the glibc
code is already in use)
next reply other threads:[~2018-05-16 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 11:10 Szabolcs Nagy [this message]
2018-05-16 11:19 ` glibc and linux-man disagrees about pkey_alloc Dmitry V. Levin
2018-05-16 11:33 ` Szabolcs Nagy
2018-05-18 15:26 ` Michael Kerrisk (man-pages)
2018-05-16 14:36 ` Florian Weimer
2018-05-16 15:18 ` Rich Felker
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=adae131e-c782-9508-808f-9cbea92ef694@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=dalias@libc.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=nd@arm.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