[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1273004694.22438.6.camel@gandalf.stny.rr.com>
Date: Tue, 04 May 2010 16:24:54 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Li Zefan <lizf@...fujitsu.com>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Subject: Re: [PATCH] tracing: Make the documentation clear on trace_event
boot option
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@...fujitsu.com>
> Signed-off-by: Li Zefan <lizf@...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
> =======================================
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists