From: Tolga Dalman <tolga.dalman-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: proc(5): minor text updates
Date: Tue, 14 Aug 2012 19:53:45 +0200 [thread overview]
Message-ID: <502A90A9.1030100@googlemail.com> (raw)
In-Reply-To: <CAKgNAkh_PxqPy+jK0t6WG54KQXOkm2JBTDw69qEtqOsaeTVGAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hello Michael,
On 08/13/12 22:41, Michael Kerrisk (man-pages) wrote:
> Ahh -- yes, an easy mistake to make I think. The thing is there are two
> unrelated sets of constants in the PF_* namespace. Take a look in
> linux/sched.h to see the other set, which is (AFAICS) the set that is used
> in this /proc file.
Which other set of PF_ constants in <linux/sched.h> ? I only see SCHED_* and
CLONE_* defined in that file. Aside from protocol family PF_* flags, there is
only <linux/elf.h> defining permission flags (PF_R/W/X), which seems unlikely
to me.
Best regards
Tolga Dalman
--
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 prev parent reply other threads:[~2012-08-14 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 19:56 proc(5): minor text updates Tolga Dalman
[not found] ` <50202153.6030808-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2012-08-13 7:35 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkhrmpZuF45iOA52akABSm4hUy4ygR=vEg4XQ_4Ri7DjRw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-13 17:13 ` Tolga Dalman
[not found] ` <502935C1.60901-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2012-08-13 20:41 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkh_PxqPy+jK0t6WG54KQXOkm2JBTDw69qEtqOsaeTVGAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-14 17:53 ` Tolga Dalman [this message]
[not found] ` <502A90A9.1030100-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2012-08-14 18:59 ` 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=502A90A9.1030100@googlemail.com \
--to=tolga.dalman-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=linux-man-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