All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: kan.liang@intel.com, mingo@redhat.com,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	eranian@google.com, tglx@linutronix.de, ak@linux.intel.com
Subject: Re: [PATCH V2 0/5] support PERF_SAMPLE_PHYS_ADDR (user)
Date: Fri, 1 Sep 2017 19:46:59 +0200	[thread overview]
Message-ID: <20170901174659.GA10349@krava> (raw)
In-Reply-To: <20170901173948.GM4831@kernel.org>

On Fri, Sep 01, 2017 at 02:39:48PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Sep 01, 2017 at 05:45:02PM +0200, Jiri Olsa escreveu:
> > On Tue, Aug 29, 2017 at 01:11:07PM -0400, kan.liang@intel.com wrote:
> > > From: Kan Liang <kan.liang@intel.com>
> > > 
> > > The patch series is to support PERF_SAMPLE_PHYS_ADDR in user perf tool.
> > > The kernel patch has been merged, which commit ID is
> > > fc7ce9c74c3a ("perf/core, x86: Add PERF_SAMPLE_PHYS_ADDR").
> > > 
> > > Changes since V1:
> > >  - Don't mandate SAMPLE_ADDR when SAMPLE_PHYS_ADDR
> > >  - Update change log
> > > 
> > > Kan Liang (5):
> > >   perf tools: support new sample type for physical address
> > >   perf tools: add sort option for physical address
> > >   perf mem: support physical address
> > >   perf script: support physical address
> > >   perf test: add test case for PERF_SAMPLE_PHYS_ADDR
> > 
> > apart from the nit in patch 1
> 
> Which I folded your patch into
> 
> > Tested/Acked-by: Jiri Olsa <jolsa@redhat.com>
> 
> I think in this case a Tested-by: is a super ack, right?
> 
> So I'll leave it as:
> 
> Tested-by: Jiri Olsa <jolsa@redhat.com>
> 
> Ok?

ook ;-)

jirka

      reply	other threads:[~2017-09-01 17:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 17:11 [PATCH V2 0/5] support PERF_SAMPLE_PHYS_ADDR (user) kan.liang
2017-08-29 17:11 ` [PATCH V2 1/5] perf tools: support new sample type for physical address kan.liang
2017-09-01 15:28   ` Jiri Olsa
2017-09-01 15:36     ` Arnaldo Carvalho de Melo
2017-09-05  5:21   ` [tip:perf/urgent] perf tools: Support " tip-bot for Kan Liang
2017-08-29 17:11 ` [PATCH V2 2/5] perf tools: add sort option " kan.liang
2017-09-05  5:21   ` [tip:perf/urgent] perf sort: Add " tip-bot for Kan Liang
2017-08-29 17:11 ` [PATCH V2 3/5] perf mem: support " kan.liang
2017-09-05  5:22   ` [tip:perf/urgent] perf mem: Support " tip-bot for Kan Liang
2017-08-29 17:11 ` [PATCH V2 4/5] perf script: support " kan.liang
2017-09-05  5:22   ` [tip:perf/urgent] perf script: Support " tip-bot for Kan Liang
2017-08-29 17:11 ` [PATCH V2 5/5] perf test: add test case for PERF_SAMPLE_PHYS_ADDR kan.liang
2017-09-05  5:23   ` [tip:perf/urgent] perf test: Add " tip-bot for Kan Liang
2017-09-01 15:45 ` [PATCH V2 0/5] support PERF_SAMPLE_PHYS_ADDR (user) Jiri Olsa
2017-09-01 17:39   ` Arnaldo Carvalho de Melo
2017-09-01 17:46     ` 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=20170901174659.GA10349@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.