From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
dev@codyps.com, 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 12:29:07 -0300 [thread overview]
Message-ID: <20150128152907.GB25018@kernel.org> (raw)
In-Reply-To: <20150128103753.GA4584@krava.brq.redhat.com>
Em Wed, Jan 28, 2015 at 11:37:53AM +0100, Jiri Olsa escreveu:
> On Wed, Jan 28, 2015 at 11:54:38AM +1100, Michael Ellerman wrote:
> > 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 ?
>
> ah right, sry ;-)
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
Thanks, I'll try and collect the tools/ bits since Michael already took
the other bits, right?
- Arnaldo
next prev parent reply other threads:[~2015-01-28 15:29 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
2015-01-28 10:37 ` Jiri Olsa
2015-01-28 15:29 ` Arnaldo Carvalho de Melo [this message]
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=20150128152907.GB25018@kernel.org \
--to=acme@kernel.org \
--cc=dev@codyps.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).