From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Vince Weaver <vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch] small flags clarficiation in perf_event_open()
Date: Tue, 21 May 2013 13:03:06 +0200 [thread overview]
Message-ID: <519B546A.60208@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1305201309150.29892-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>
On 05/20/13 19:11, Vince Weaver wrote:
>
> While using the perf_event_open() manpage to enhance the trinity fuzzer
> I noticed the statement about the "flags" argument was misleading.
>
> Signed-off-by: Vince Weaver <vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
>
> diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
> index f3850f0..14fb854 100644
> --- a/man2/perf_event_open.2
> +++ b/man2/perf_event_open.2
> @@ -148,7 +148,9 @@ instructions.
> .P
> The
> .I flags
> -argument takes one of the following values:
> +argument takes a
> +.RI bitwise- or 'd
> +combination of zero or more of the following values:
> .TP
> .BR PERF_FLAG_FD_NO_GROUP
> .\" FIXME The following sentence is unclear
>
Thanks, Vince. I made it
====
The
.I flags
argument is formed by ORing together zero or more of the following values:
====
Cheers,
Michael
--
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
prev parent reply other threads:[~2013-05-21 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 17:11 [patch] small flags clarficiation in perf_event_open() Vince Weaver
[not found] ` <alpine.DEB.2.02.1305201309150.29892-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>
2013-05-21 11:03 ` Michael Kerrisk [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=519B546A.60208@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.