[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150227123232.GC2877@e104805>
Date: Fri, 27 Feb 2015 12:32:32 +0000
From: Javi Merino <javi.merino@....com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Namhyung Kim <namhyung@...nel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Jiri Olsa <jolsa@...hat.com>,
Punit Agrawal <Punit.Agrawal@....com>
Subject: Re: [PATCH v5 3/3] tools lib traceevent: Add support for
__print_array()
Hi Steve,
On Wed, Jan 28, 2015 at 12:48:55PM +0000, Javi Merino wrote:
> Trace can now generate traces with variable element size arrays. Add
> support to parse them.
>
> Cc: Namhyung Kim <namhyung@...nel.org>
> Cc: Arnaldo Carvalho de Melo <acme@...hat.com>
> Cc: Steven Rostedt <rostedt@...dmis.org>
> Cc: Jiri Olsa <jolsa@...hat.com>
> Signed-off-by: Javi Merino <javi.merino@....com>
> ---
> tools/lib/traceevent/event-parse.c | 93 ++++++++++++++++++++++++++++++++++++++
> tools/lib/traceevent/event-parse.h | 8 ++++
> 2 files changed, 101 insertions(+)
I've seen that patch 1 of this series is now in mainline. What about
patches 2 and 3 (the updates to tools/lib/traceevent)? Shall I resend
them?
These two patches should also be applied to trace-cmd. Do you want me
to send patches for that to linux-kernel or will you take care of
applying them there?
Incidentally, why are there two copies of libtraceevent? Shouldn't
this live only in one place (either kernel or trace-cmd)?
Cheers,
Javi
--
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