From: Will Deacon <will.deacon@arm.com>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: Jean Pihet <jean.pihet@linaro.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Mark Rutland <Mark.Rutland@arm.com>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
Steve Capper <steve.capper@linaro.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Patch Tracking <patches@linaro.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] perf tests: Introduce perf_regs_load function on ARM64
Date: Tue, 6 May 2014 09:51:44 +0100 [thread overview]
Message-ID: <20140506085144.GA26592@arm.com> (raw)
In-Reply-To: <CAORVsuV5qYKLd21YSJhLy7Ovi5s4sXUEgbNot7LJspNnbdBpFw@mail.gmail.com>
On Mon, May 05, 2014 at 08:07:11AM +0100, Jean Pihet wrote:
> Hi Will,
>
> On Fri, May 2, 2014 at 6:51 PM, Will Deacon <will.deacon@arm.com> wrote:
> > On Fri, May 02, 2014 at 10:19:38AM +0100, Jean Pihet wrote:
> >> Hi WIll, Mark,
> >>
> >> Ping on this series. Can you please check? Is the refreshed patch OK?
> >
> > Fine by me, as long as it's not reused outside of this test :)
> Great! Is there some precaution to avoid a mis-reuse?
Hopefully your comment will be enough.
> Other than that, which tree are the patches going to?
They're all under perf/tools/, so they should go via that tree.
Will
next prev parent reply other threads:[~2014-05-06 8:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 9:42 [PATCH 0/3] perf tools: Add libdw DWARF post unwind support for ARM64 Jean Pihet
2014-03-19 9:42 ` [PATCH 1/3] perf tests: Introduce perf_regs_load function on ARM64 Jean Pihet
2014-03-21 15:11 ` Mark Rutland
2014-03-25 15:23 ` Jean Pihet
2014-04-04 7:51 ` Jean Pihet
2014-04-22 8:13 ` Jean Pihet
2014-04-22 10:37 ` Will Deacon
2014-04-22 13:24 ` Mark Rutland
2014-04-22 13:42 ` Mark Rutland
2014-04-28 13:10 ` Jean Pihet
2014-04-28 13:12 ` Jean Pihet
2014-05-02 9:19 ` Jean Pihet
2014-05-02 16:51 ` Will Deacon
2014-05-05 7:07 ` Jean Pihet
2014-05-06 8:51 ` Will Deacon [this message]
2014-03-19 9:42 ` [PATCH 2/3] perf tests: Add dwarf unwind test " Jean Pihet
2014-03-19 9:42 ` [PATCH 3/3] perf tools: Add libdw DWARF post unwind support for ARM64 Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2014-05-06 15:55 [PATCH 0/3] " Jean Pihet
2014-05-06 15:55 ` [PATCH 1/3] perf tests: Introduce perf_regs_load function on ARM64 Jean Pihet
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=20140506085144.GA26592@arm.com \
--to=will.deacon@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=acme@infradead.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jean.pihet@linaro.org \
--cc=jean.pihet@newoldbits.com \
--cc=jolsa@redhat.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=patches@linaro.org \
--cc=paulus@samba.org \
--cc=steve.capper@linaro.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