From: "Jörn Engel" <joern@purestorage.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: get_mempolicy(2) type mismatch
Date: Mon, 2 May 2016 17:58:21 -0700 [thread overview]
Message-ID: <20160503005821.GC9613@cork> (raw)
The manpage seems to have the wrong type for "addr".
Manpage:
int get_mempolicy(int *mode, unsigned long *nodemask,
unsigned long maxnode, unsigned long addr,
unsigned long flags);
/usr/include/numaif.h:
extern long get_mempolicy(int *policy, const unsigned long *nmask,
unsigned long maxnode, void *addr, int flags);
J�rn
--
The more any quantitative social indicator is used for social decision-making,
the more subject it will be to corruption pressures and the more apt it will
be to distort and corrupt the social processes it is intended to monitor.
-- Campbell's law
next reply other threads:[~2016-05-03 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 0:58 Jörn Engel [this message]
2016-06-03 2:19 ` get_mempolicy(2) type mismatch Michael Kerrisk (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=20160503005821.GC9613@cork \
--to=joern@purestorage.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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 NNTP newsgroup(s).