public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Namhyung Kim <namhyung.kim@lge.com>
Subject: Re: [PATCH 2/2] perf header: Prepare tracepoint events regardless of name
Date: Thu, 6 Sep 2012 06:51:38 -0700	[thread overview]
Message-ID: <20120906135137.GJ8203@ghostprotocols.net> (raw)
In-Reply-To: <1346897446-16569-2-git-send-email-namhyung@kernel.org>

Em Thu, Sep 06, 2012 at 11:10:46AM +0900, Namhyung Kim escreveu:
> From: Namhyung Kim <namhyung.kim@lge.com>
> 
> Current perf_evlist__set_tracepoint_names is a misnomer because it
> finds and sets correspoding event_format in addition to the name.  So
> skipping it when a event has set name already caused a trouble.
> 
> Rename it and set name only a event doesn't have one.
> 
> Reported-by: David Ahern <dsahern@gmail.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> Arnaldo, I made it incremental for your convenience.  But if you want
> to drop my previous one I can resend with it.  Please let me know your
> preference. :)

I applied this 2-patch series now, thanks.

- Arnaldo

  reply	other threads:[~2012-09-06 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  2:10 [PATCH 1/2] perf header: Fix a typo on evsel Namhyung Kim
2012-09-06  2:10 ` [PATCH 2/2] perf header: Prepare tracepoint events regardless of name Namhyung Kim
2012-09-06 13:51   ` Arnaldo Carvalho de Melo [this message]
2012-09-07  6:12   ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-09-07  6:12 ` [tip:perf/core] perf header: Fix a typo on evsel tip-bot for Namhyung Kim

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=20120906135137.GJ8203@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.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