From: Ingo Molnar <mingo@kernel.org>
To: Will Deacon <will.deacon@arm.com>
Cc: Jean Pihet <jean.pihet@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Arnaldo <acme@ghostprotocols.net>, Jiri Olsa <jolsa@redhat.com>,
Patch Tracking <patches@linaro.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] perf: ARM64: wire up perf_regs and unwind support
Date: Wed, 12 Feb 2014 12:27:44 +0100 [thread overview]
Message-ID: <20140212112744.GA10517@gmail.com> (raw)
In-Reply-To: <20140212101011.GC13441@mudshark.cambridge.arm.com>
* Will Deacon <will.deacon@arm.com> wrote:
> On Wed, Feb 12, 2014 at 08:46:38AM +0000, Jean Pihet wrote:
> > Hi Arnaldo, Will,
> >
> > Ping on this patch.
>
> This needs to go via the perf tree to avoid a repeat of the mess last time.
If the tooling bits are fine with Arnaldo then I have no objections
either - once all the bits are acked please send a single series with
all 4(?) patches in it, for tip:perf/core inclusion.
Thanks,
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: mingo@kernel.org (Ingo Molnar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] perf: ARM64: wire up perf_regs and unwind support
Date: Wed, 12 Feb 2014 12:27:44 +0100 [thread overview]
Message-ID: <20140212112744.GA10517@gmail.com> (raw)
In-Reply-To: <20140212101011.GC13441@mudshark.cambridge.arm.com>
* Will Deacon <will.deacon@arm.com> wrote:
> On Wed, Feb 12, 2014 at 08:46:38AM +0000, Jean Pihet wrote:
> > Hi Arnaldo, Will,
> >
> > Ping on this patch.
>
> This needs to go via the perf tree to avoid a repeat of the mess last time.
If the tooling bits are fine with Arnaldo then I have no objections
either - once all the bits are acked please send a single series with
all 4(?) patches in it, for tip:perf/core inclusion.
Thanks,
Ingo
next prev parent reply other threads:[~2014-02-12 11:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 18:17 [PATCH] perf: ARM64: wire up perf_regs and unwind support Jean Pihet
2014-02-03 18:17 ` Jean Pihet
2014-02-12 8:46 ` Jean Pihet
2014-02-12 8:46 ` Jean Pihet
2014-02-12 10:10 ` Will Deacon
2014-02-12 10:10 ` Will Deacon
2014-02-12 11:27 ` Ingo Molnar [this message]
2014-02-12 11:27 ` Ingo Molnar
2014-02-12 11:30 ` Will Deacon
2014-02-12 11:30 ` Will Deacon
2014-02-12 13:02 ` Arnaldo Carvalho de Melo
2014-02-12 13:02 ` Arnaldo Carvalho de Melo
2014-02-12 13:09 ` Jiri Olsa
2014-02-12 13:09 ` Jiri Olsa
2014-02-13 17:01 ` Jean Pihet
2014-02-13 17:01 ` Jean Pihet
2014-02-13 17:06 Jean Pihet
2014-02-13 17:06 ` Jean Pihet
2014-03-12 12:42 ` Jean Pihet
2014-03-12 12:42 ` Jean Pihet
2014-03-12 17:45 ` Catalin Marinas
2014-03-12 17:45 ` Catalin Marinas
2014-03-13 10:12 ` Will Deacon
2014-03-13 10:12 ` Will Deacon
2014-03-13 10:22 ` Catalin Marinas
2014-03-13 10:22 ` Catalin Marinas
2014-03-13 12:01 ` Jean Pihet
2014-03-13 12:01 ` Jean Pihet
2014-04-28 9:15 ` Jean Pihet
2014-04-28 9:15 ` Jean Pihet
2014-04-28 9:24 ` Jiri Olsa
2014-04-28 9:24 ` Jiri Olsa
2014-04-28 12:32 ` Jean Pihet
2014-04-28 12:32 ` 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=20140212112744.GA10517@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=jean.pihet@linaro.org \
--cc=jolsa@redhat.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.