linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Anju T <anju@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, maddy@linux.vnet.ibm.com,
	jolsa@redhat.com, dsahern@gmail.com, sukadev@linux.vnet.ibm.com,
	hemant@linux.vnet.ibm.com, acme@kernel.org,
	naveen.n.rao@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V11 0/4]perf/powerpc: Add ability to sample intr machine state in powerpc
Date: Wed, 20 Apr 2016 10:16:33 -0300	[thread overview]
Message-ID: <20160420131633.GI2527@redhat.com> (raw)
In-Reply-To: <1461128158.13404.3.camel@ellerman.id.au>

Em Wed, Apr 20, 2016 at 02:55:58PM +1000, Michael Ellerman escreveu:
> On Wed, 2016-04-20 at 00:57 -0300, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Apr 18, 2016 at 03:17:11PM +0530, Anju T escreveu:
> > > On Saturday 20 February 2016 10:32 AM, Anju T wrote:
> > > >  tools/perf/arch/powerpc/include/perf_regs.h | 69 ++++++++++++++++++++++
> > > >  tools/perf/arch/powerpc/util/Build          |  1 +
> > > >  tools/perf/arch/powerpc/util/perf_regs.c    | 49 ++++++++++++++++
> > > >  tools/perf/config/Makefile                  |  5 ++
> > > >  create mode 100644 tools/perf/arch/powerpc/include/perf_regs.h
> > > >  create mode 100644 tools/perf/arch/powerpc/util/perf_regs.c

> > > Can this be taken into the next tree?

> > Even the bits in tools/perf/ are arch specific, so I guess this goes via
> > the powerpc tree? Michael?

> Yeah if that's OK with you.
> 
> It doesn't look like it will generate much in the way of merge conflicts.
> 
> Do you want to send an ack?

For the tools/perf/ bits:

Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>

- Arnaldo

  reply	other threads:[~2016-04-20 13:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20  5:02 [PATCH V11 0/4]perf/powerpc: Add ability to sample intr machine state in powerpc Anju T
2016-02-20  5:02 ` [PATCH V11 1/4] perf/powerpc: assign an id to each powerpc register Anju T
2016-04-21 11:07   ` Naveen N. Rao
2016-04-21 13:39   ` [V11,1/4] " Michael Ellerman
2016-02-20  5:02 ` [PATCH V11 2/4] perf/powerpc: add support for sampling intr machine state Anju T
2016-04-21 11:15   ` Naveen N. Rao
2016-04-21 13:39   ` [V11, " Michael Ellerman
2016-02-20  5:02 ` [PATCH V11 3/4] tools/perf: Map the ID values with register names Anju T
2016-04-21 13:39   ` [V11,3/4] " Michael Ellerman
2016-02-20  5:02 ` [PATCH V2 4/4] tool/perf: Add sample_reg_mask to include all perf_regs Anju T
2016-04-21 13:39   ` [V2,4/4] " Michael Ellerman
2016-03-07  8:23 ` [PATCH V11 0/4]perf/powerpc: Add ability to sample intr machine state in powerpc Anju T
2016-04-18  9:47 ` Anju T
2016-04-20  3:57   ` Arnaldo Carvalho de Melo
2016-04-20  4:55     ` Michael Ellerman
2016-04-20 13:16       ` Arnaldo Carvalho de Melo [this message]
2016-04-21 13:41         ` Michael Ellerman

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=20160420131633.GI2527@redhat.com \
    --to=acme@redhat.com \
    --cc=acme@kernel.org \
    --cc=anju@linux.vnet.ibm.com \
    --cc=dsahern@gmail.com \
    --cc=hemant@linux.vnet.ibm.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --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).