public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Javi Merino <javi.merino@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>,
	Punit Agrawal <Punit.Agrawal@arm.com>
Subject: Re: [PATCH v5 3/3] tools lib traceevent: Add support for __print_array()
Date: Fri, 27 Feb 2015 12:32:32 +0000	[thread overview]
Message-ID: <20150227123232.GC2877@e104805> (raw)
In-Reply-To: <1422449335-8289-4-git-send-email-javi.merino@arm.com>

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@kernel.org>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Jiri Olsa <jolsa@redhat.com>
> Signed-off-by: Javi Merino <javi.merino@arm.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

  reply	other threads:[~2015-02-27 12:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 12:48 [PATCH v5 0/3] Add array printing helper to ftrace Javi Merino
2015-01-28 12:48 ` [PATCH v5 1/3] tracing: Add array printing helper Javi Merino
2015-01-28 12:48 ` [PATCH v5 2/3] tools lib traceevent: factor out allocating and processing args Javi Merino
2015-01-28 12:48 ` [PATCH v5 3/3] tools lib traceevent: Add support for __print_array() Javi Merino
2015-02-27 12:32   ` Javi Merino [this message]
2015-02-27 14:15     ` Steven Rostedt
2015-02-27 14:52       ` Javi Merino
2015-06-04 14:25       ` Javi Merino
2015-06-08 16:17         ` Steven Rostedt
2015-07-13 16:06         ` Steven Rostedt
2015-07-13 16:36           ` Javi Merino

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=20150227123232.GC2877@e104805 \
    --to=javi.merino@arm.com \
    --cc=Punit.Agrawal@arm.com \
    --cc=acme@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.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