public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman•id.au>
To: Jiri Olsa <jolsa@redhat•com>
Cc: peterz@infradead•org, linux-kernel@vger•kernel.org,
	Arnaldo Carvalho de Melo <acme@kernel•org>,
	dev@codyps•com, Paul Mackerras <paulus@samba•org>,
	Sukadev Bhattiprolu <sukadev@linux•vnet.ibm.com>,
	linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH v7 0/4] Add support for parametrized events
Date: Wed, 28 Jan 2015 11:54:38 +1100	[thread overview]
Message-ID: <1422406478.32234.0.camel@ellerman.id.au> (raw)
In-Reply-To: <20150127100213.GC7810@krava.brq.redhat.com>

On Tue, 2015-01-27 at 11:02 +0100, Jiri Olsa wrote:
> On Mon, Jan 26, 2015 at 05:43:03PM -0800, Sukadev Bhattiprolu wrote:
> 
> SNIP
> 
> > 
> > 
> > Cody P Schafer (6):
> >   perf: provide sysfs_show for struct perf_pmu_events_attr
> >   perf: add PMU_EVENT_ATTR_STRING() helper
> >   powerpc/perf/hv-24x7: parse catalog and populate sysfs with events
> >   powerpc/perf/{hv-gpci, hv-common}: generate requests with counters
> >     annotated
> >   powerpc/perf/hv-gpci: add the remaining gpci requests
> >   powerpc/perf/hv-24x7: Document sysfs event description entries
> > 
> > Sukadev Bhattiprolu (1):
> >   perf: define EVENT_DEFINE_RANGE_FORMAT_LITE helper
> 
> generic 'perf: *' patches look good to me.. cant say much about
> the rest of the patchset though

Is that an ACK ?

I'm happy to merge the rest through the powerpc tree, but I'd like an ACK on
the first two from someone in perf land.

cheers

  reply	other threads:[~2015-01-28  0:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  1:43 [PATCH v7 0/4] Add support for parametrized events Sukadev Bhattiprolu
2015-01-27  1:43 ` [PATCH v7 1/7] perf: provide sysfs_show for struct perf_pmu_events_attr Sukadev Bhattiprolu
2015-01-27  1:43 ` [PATCH v7 2/7] perf: add PMU_EVENT_ATTR_STRING() helper Sukadev Bhattiprolu
2015-01-27  1:43 ` [PATCH v7 3/7] perf: define EVENT_DEFINE_RANGE_FORMAT_LITE helper Sukadev Bhattiprolu
2015-01-27  1:43 ` [PATCH v7 4/7] powerpc/perf/hv-24x7: parse catalog and populate sysfs with events Sukadev Bhattiprolu
2015-01-27  1:43 ` [PATCH v7 5/7] powerpc/perf/{hv-gpci, hv-common}: generate requests with counters annotated Sukadev Bhattiprolu
2015-01-27  1:43 ` [PATCH v7 6/7] powerpc/perf/hv-gpci: add the remaining gpci requests Sukadev Bhattiprolu
2015-01-27  1:43 ` [PATCH v7 7/7] powerpc/perf/hv-24x7: Document sysfs event description entries Sukadev Bhattiprolu
2015-01-27 10:02 ` [PATCH v7 0/4] Add support for parametrized events Jiri Olsa
2015-01-28  0:54   ` Michael Ellerman [this message]
2015-01-28 10:37     ` Jiri Olsa
2015-01-28 15:29       ` Arnaldo Carvalho de Melo
2015-01-29  4:24       ` Michael Ellerman
2015-01-29  4:28 ` Michael Ellerman
2015-01-30 14:52   ` Arnaldo Carvalho de Melo
2015-02-02  1:15     ` Michael Ellerman
  -- strict thread matches above, loose matches on Subject: below --
2015-01-30 21:45 Sukadev Bhattiprolu
2015-01-08  1:13 Sukadev Bhattiprolu
2015-01-08  9:54 ` Jiri Olsa
2015-01-12 14:18   ` Arnaldo Carvalho de Melo

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=1422406478.32234.0.camel@ellerman.id.au \
    --to=mpe@ellerman$(echo .)id.au \
    --cc=acme@kernel$(echo .)org \
    --cc=dev@codyps$(echo .)com \
    --cc=jolsa@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=paulus@samba$(echo .)org \
    --cc=peterz@infradead$(echo .)org \
    --cc=sukadev@linux$(echo .)vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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