From: Steven Rostedt <rostedt@goodmis.org>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [PATCH] tracing: Make the documentation clear on trace_event boot option
Date: Tue, 04 May 2010 16:24:54 -0400 [thread overview]
Message-ID: <1273004694.22438.6.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4B2F154C.2060503@cn.fujitsu.com>
Going through old email, I came across this. Looks like it was never
applied, I'll pull it in. I think I was on vacation when this was
received, and got lost it the masses.
Sorry for the --very-- late response.
-- Steve
On Mon, 2009-12-21 at 14:27 +0800, Li Zefan wrote:
> Make it clear that event-list is a comma separated list of events.
>
> Reported-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
> Documentation/trace/events.txt | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/trace/events.txt b/Documentation/trace/events.txt
> index 02ac6ed..778ddf3 100644
> --- a/Documentation/trace/events.txt
> +++ b/Documentation/trace/events.txt
> @@ -90,7 +90,8 @@ In order to facilitate early boot debugging, use boot option:
>
> trace_event=[event-list]
>
> -The format of this boot option is the same as described in section 2.1.
> +event-list is a comma separated list of events. See section 2.1 for event
> +format.
>
> 3. Defining an event-enabled tracepoint
> =======================================
next prev parent reply other threads:[~2010-05-04 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 6:27 Li Zefan
2010-05-04 20:24 ` Steven Rostedt [this message]
2010-05-07 18:39 ` [tip:tracing/core] " tip-bot for Li Zefan
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=1273004694.22438.6.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®