public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@redhat.com>,
	acme@kernel.org, namhyung@kernel.org, eranian@google.com,
	linux-kernel@vger.kernel.org, mingo@kernel.org
Subject: Re: More updates for event lists in perf list
Date: Mon, 1 Jun 2015 10:52:26 +0200	[thread overview]
Message-ID: <20150601085226.GA19893@krava.redhat.com> (raw)
In-Reply-To: <20150601033310.GA1503@us.ibm.com>

On Sun, May 31, 2015 at 08:33:10PM -0700, Sukadev Bhattiprolu wrote:
> Andi Kleen [andi@firstfloor.org] wrote:
> | This adds support for the event topics that Ingo requested, and
> | replaces the earlier event group patch. JSON files now have a Topic
> | header that is used by perf list to group events.
> | 
> | This applies on top of Sukadev's patchkit. In addition
> | the Intel events also need to be pulled from 
> | 
> | git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git perf/intel-json-files-3
> 
> I addressed comments, rebased to Arnaldo's tree and pushed all patches to:
> 
> 	https://github.com/sukadev/linux.git
> 
> Branches:
> 
> 	json-v12		(code only)
> 	json-files-3		(x86 and powerpc data files only)

please make also one merged branch and advertise
it in the patchset.. so people can do just single
checkout and try the code with data files

thanks,
jirka

      reply	other threads:[~2015-06-01  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 16:11 More updates for event lists in perf list Andi Kleen
2015-05-31 16:11 ` [PATCH 1/3] perf, tools: Add override support for event list CPUID Andi Kleen
2015-06-01 10:29   ` Jiri Olsa
2015-05-31 16:11 ` [PATCH 2/3] perf, tools: Support long descriptions with perf list -v Andi Kleen
2015-05-31 16:11 ` [PATCH 3/3] perf, tools: Add support for event list topics Andi Kleen
2015-06-01  3:33 ` More updates for event lists in perf list Sukadev Bhattiprolu
2015-06-01  8:52   ` Jiri Olsa [this message]

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=20150601085226.GA19893@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=sukadev@linux.vnet.ibm.com \
    /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