From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Anton Blanchard <anton@samba.org>
Cc: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
bsingharora@gmail.com, naveen.n.rao@linux.vnet.ibm.com,
ananth@in.ibm.com, mhiramat@kernel.org, wangnan0@huawei.com,
namhyung@kernel.org
Subject: Re: [PATCH 2/2] perf ppc64le: Fix probe location when using DWARF
Date: Fri, 12 Aug 2016 10:01:46 -0300 [thread overview]
Message-ID: <20160812130146.GJ27651@kernel.org> (raw)
In-Reply-To: <20160812160655.7f250d21@kryten>
Em Fri, Aug 12, 2016 at 04:06:55PM +1000, Anton Blanchard escreveu:
> Hi Arnaldo,
>
> > Anyway, Anton, does this fix the problem for you?
>
> Yes it does, thanks!
Thanks, adding a Tested-by: you.
- Arnaldo
next prev parent reply other threads:[~2016-08-12 13:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 6:23 [PATCH 1/2] perf: Add function to post process kernel trace events Ravi Bangoria
2016-08-09 6:23 ` [PATCH 2/2] perf ppc64le: Fix probe location when using DWARF Ravi Bangoria
2016-08-09 14:02 ` Masami Hiramatsu
2016-08-09 15:09 ` Arnaldo Carvalho de Melo
2016-08-09 19:21 ` [tip:perf/urgent] perf probe " tip-bot for Ravi Bangoria
2016-08-10 23:54 ` [PATCH 2/2] perf " Anton Blanchard
2016-08-11 4:31 ` Ravi Bangoria
2016-08-11 11:50 ` Arnaldo Carvalho de Melo
2016-08-11 13:21 ` Ravi Bangoria
2016-08-11 14:49 ` Arnaldo Carvalho de Melo
2016-08-11 17:40 ` Arnaldo Carvalho de Melo
2016-08-12 6:06 ` Anton Blanchard
2016-08-12 13:01 ` Arnaldo Carvalho de Melo [this message]
2016-08-16 18:14 ` [tip:perf/urgent] perf ppc64le: Fix build failure when libelf is not present tip-bot for Ravi Bangoria
2016-08-11 15:49 ` [PATCH 2/2] perf ppc64le: Fix probe location when using DWARF Arnaldo Carvalho de Melo
2016-08-09 19:20 ` [tip:perf/urgent] perf probe: Add function to post process kernel trace events tip-bot for Ravi Bangoria
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=20160812130146.GJ27651@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth@in.ibm.com \
--cc=anton@samba.org \
--cc=bsingharora@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.vnet.ibm.com \
--cc=wangnan0@huawei.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).