From: Vlastimil Babka <vbabka-AlSwsSmVLrQ@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-numa-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Missing include in mbind(2) and set_mempolicy(2) manpages?
Date: Wed, 18 Jan 2017 13:05:17 +0100 [thread overview]
Message-ID: <1d46ea2d-0076-603d-d922-1f414c91cea2@suse.cz> (raw)
Hi,
the two manpages state that you have to #include <numaif.h>
But apparently this is not enough when one wants to use the MPOL_F_STATIC_NODES
or MPOL_F_RELATIVE_NODES flag. With grep I found that these are defined in
linux/mempolicy.h.
This is on openSUSE Tumbleweed, numaif.h comes from
libnuma-devel-2.0.10-5.7.x86_64 (I checked upstream 2.0.11 tarball, no
difference here).
linux/mempolicy.h is from linux-glibc-devel-4.8-1.1.noarch
Thanks,
Vlastimil
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-01-18 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 12:05 Vlastimil Babka [this message]
[not found] ` <1d46ea2d-0076-603d-d922-1f414c91cea2-AlSwsSmVLrQ@public.gmane.org>
2017-01-22 23:57 ` Missing include in mbind(2) and set_mempolicy(2) manpages? Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkhBRXm22fBS72T4CP6RutEubaqyDFUJe4gwje_irATzkQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-19 13:28 ` 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=1d46ea2d-0076-603d-d922-1f414c91cea2@suse.cz \
--to=vbabka-alswssmvlrq@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-numa-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).