From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"eranian@google.com" <eranian@google.com>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
"dsahern@gmail.com" <dsahern@gmail.com>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 1/3] perf,tools: get correct cpu id for print_aggr
Date: Fri, 28 Aug 2015 11:47:19 -0300 [thread overview]
Message-ID: <20150828144719.GG31339@kernel.org> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F077018F4AC2@SHSMSX103.ccr.corp.intel.com>
Em Fri, Aug 28, 2015 at 02:39:21PM +0000, Liang, Kan escreveu:
> > In this case it needs to go to perf/urgent, where it applies
> > cleanly, perf/core has extra stuff there that fuzzes a bit.
> > Also, since you know the cset where this bug was introduced, please
> > consider adding a "Fixes:" tag, commom everywhere in the kernel:
> OK. I think this patch needs to go to perf/urgent.
> Should I re-send this patch with "Fixes:" tag and comments?
No need, I did this already, its sitting in my perf/urgent branch now,
will go to Ingo today.
- Arnaldo
next prev parent reply other threads:[~2015-08-28 14:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 7:08 [PATCH V2 1/3] perf,tools: get correct cpu id for print_aggr kan.liang
2015-07-02 7:08 ` [PATCH V2 2/3] perf,tools: check and re-organize evsel cpu maps kan.liang
2015-07-15 21:14 ` Liang, Kan
2015-07-02 7:08 ` [PATCH V2 3/3] perf,tests: Add cpu_map tests kan.liang
2015-07-02 16:12 ` Jiri Olsa
2015-07-02 16:58 ` Liang, Kan
2015-07-02 16:13 ` [PATCH V2 1/3] perf,tools: get correct cpu id for print_aggr Jiri Olsa
2015-08-28 13:33 ` Liang, Kan
2015-08-28 14:23 ` acme
2015-08-28 14:39 ` Liang, Kan
2015-08-28 14:45 ` Stephane Eranian
2015-08-28 14:47 ` Arnaldo Carvalho de Melo [this message]
2015-08-28 14:51 ` Liang, Kan
2015-08-31 8:27 ` [tip:perf/urgent] perf stat: Get " 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=20150828144719.GG31339@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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