public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	"jolsa@kernel.org" <jolsa@kernel.org>,
	"ak@linux.intel.com" <ak@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4 3/3] perf,test: test cpu topology
Date: Wed, 2 Sep 2015 08:03:08 +0200	[thread overview]
Message-ID: <20150902060308.GD1978@krava.brq.redhat.com> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F077018F5D2E@SHSMSX103.ccr.corp.intel.com>

On Tue, Sep 01, 2015 at 11:25:10PM +0000, Liang, Kan wrote:
> 
> 
> > 
> > Em Tue, Sep 01, 2015 at 09:58:13AM -0400, Kan Liang escreveu:
> > > From: Jiri Olsa <jolsa@kernel.org>
> > >
> > > This patch test cpu core_id and socket_id which are stored in perf_env.
> > >
> > > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > > Signed-off-by: Kan Liang <kan.liang@intel.com>
> > > ---
> > >
> > > Changes since jirka's original version
> > >  - Use pr_debug to replace fprintf
> > >  - Add date_size to avoid warning
> > >  - Introduce cpu_map, and compare core_id and socket_id
> > >    between cpu_map and perf_env
> > 
> > Humm, two questions:
> > 
> > Since you changed it that much, wouldn't be better to give you the
> > authorship while still giving credit to Jiri for the original version?
> > Something like:
> > 
> > Based-on-a-patch-by: Jiri Olsa
> 
> Jiri, are you OK with that?

yep

> 
> > 
> > [acme@zoo linux]$ git log | grep Based-on-patch-by: | wc -l
> > 61
> > [acme@zoo linux]$ git log | grep Based-on-a-patch-by: | wc -l
> > 4
> > [acme@zoo linux]$
> > 
> > But then you need to resubmit this anyway, as you forgot to do the:
> > 
> >  git add tools/perf/tests/topology.c
> 
> Ah... My bad. :(
> 
> I will resubmit the patch then.

I'll review new version

jirka

  reply	other threads:[~2015-09-02  6:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 13:58 [PATCH V4 1/3] perf,tools: Separated functions to get core_id and socket_id Kan Liang
2015-09-01 13:58 ` [PATCH V4 2/3] perf,tools: store cpu socket_id and core_id in perf.date Kan Liang
2015-09-01 22:24   ` Arnaldo Carvalho de Melo
2015-09-08 14:32   ` [tip:perf/core] perf tools: Store the cpu socket and core ids in the perf.data header tip-bot for Kan Liang
2015-09-01 13:58 ` [PATCH V4 3/3] perf,test: test cpu topology Kan Liang
2015-09-01 22:29   ` Arnaldo Carvalho de Melo
2015-09-01 23:25     ` Liang, Kan
2015-09-02  6:03       ` Jiri Olsa [this message]
2015-09-08 14:31 ` [tip:perf/core] perf cpumap: Factor out functions to get core_id and socket_id tip-bot for Kan Liang

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=20150902060308.GD1978@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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