From: "Liang, Kan" <kan.liang@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "acme@kernel.org" <acme@kernel.org>,
"jolsa@redhat.com" <jolsa@redhat.com>,
"eranian@google.com" <eranian@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"paulus@samba.org" <paulus@samba.org>,
"ak@linux.intel.com" <ak@linux.intel.com>
Subject: RE: [PATCH 0/2] perf tool: Haswell LBR call stack support (user)
Date: Mon, 10 Nov 2014 14:08:38 +0000 [thread overview]
Message-ID: <37D7C6CF3E00A74B8858931C1DB2F0770165F29D@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20141110105428.GH3337@twins.programming.kicks-ass.net>
> acme, jolsa, ACK on these two?
These patches are pure user tool patches. I usually sent the tool
patches to them for review. Also, Jolsa had some comments on
the previous perf tool part. So I would like them have a look
at the new changes of the user tool.
Thanks,
Kan
prev parent reply other threads:[~2014-11-10 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 14:58 [PATCH 0/2] perf tool: Haswell LBR call stack support (user) kan.liang
2014-11-06 14:58 ` [PATCH 1/2] perf tools: enable LBR call stack support kan.liang
2014-11-12 7:50 ` Jiri Olsa
2014-11-12 7:50 ` Jiri Olsa
2014-11-12 14:44 ` Liang, Kan
2014-11-06 14:58 ` [PATCH 2/2] perf tools: Construct LBR call chain kan.liang
2014-11-12 8:58 ` Jiri Olsa
2014-11-12 8:58 ` Jiri Olsa
2014-11-12 8:59 ` Jiri Olsa
2014-11-12 14:37 ` Liang, Kan
2014-11-12 15:05 ` Peter Zijlstra
2014-11-12 18:31 ` Jiri Olsa
2014-11-12 12:33 ` Jiri Olsa
2014-11-10 10:54 ` [PATCH 0/2] perf tool: Haswell LBR call stack support (user) Peter Zijlstra
2014-11-10 14:08 ` Liang, Kan [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=37D7C6CF3E00A74B8858931C1DB2F0770165F29D@SHSMSX103.ccr.corp.intel.com \
--to=kan.liang@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).