From: Paul Mackerras <paulus@samba.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
linuxppc-dev@ozlabs.org, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Anton Blanchard <anton@samba.org>
Subject: Re: [GIT PULL] perf_event/tracing/powerpc patches from Anton Blanchard
Date: Thu, 29 Oct 2009 13:43:44 +1100 [thread overview]
Message-ID: <19177.352.47019.4942@drongo.ozlabs.ibm.com> (raw)
In-Reply-To: <1256780668.26770.15.camel@pasglop>
Benjamin Herrenschmidt writes:
> On Thu, 2009-10-29 at 11:56 +1100, Paul Mackerras wrote:
> > Here is a series of patches from Anton Blanchard that implement some
> > nice tracing and perf_event features on powerpc. One of them is
> > generic perf_event stuff (adding software events for alignment faults
> > and instruction emulation faults).
> >
> > Since this touches the perf_event and tracing subsystems as well as the
> > powerpc architecture code, I think the best way forward is for both
> > Ingo and Ben to pull it into their trees. I have based it on the most
> > recent point in Linus' tree that Ingo had pulled into his perf
> > branches (as of yesterday or so).
>
> This is -next material right ?
Yes, please pull it into your next branch.
Thanks,
Paul.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mackerras <paulus@samba.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [GIT PULL] perf_event/tracing/powerpc patches from Anton Blanchard
Date: Thu, 29 Oct 2009 13:43:44 +1100 [thread overview]
Message-ID: <19177.352.47019.4942@drongo.ozlabs.ibm.com> (raw)
In-Reply-To: <1256780668.26770.15.camel@pasglop>
Benjamin Herrenschmidt writes:
> On Thu, 2009-10-29 at 11:56 +1100, Paul Mackerras wrote:
> > Here is a series of patches from Anton Blanchard that implement some
> > nice tracing and perf_event features on powerpc. One of them is
> > generic perf_event stuff (adding software events for alignment faults
> > and instruction emulation faults).
> >
> > Since this touches the perf_event and tracing subsystems as well as the
> > powerpc architecture code, I think the best way forward is for both
> > Ingo and Ben to pull it into their trees. I have based it on the most
> > recent point in Linus' tree that Ingo had pulled into his perf
> > branches (as of yesterday or so).
>
> This is -next material right ?
Yes, please pull it into your next branch.
Thanks,
Paul.
next prev parent reply other threads:[~2009-10-29 2:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 0:56 [GIT PULL] perf_event/tracing/powerpc patches from Anton Blanchard Paul Mackerras
2009-10-29 0:56 ` Paul Mackerras
2009-10-29 1:44 ` Benjamin Herrenschmidt
2009-10-29 1:44 ` Benjamin Herrenschmidt
2009-10-29 2:43 ` Paul Mackerras [this message]
2009-10-29 2:43 ` Paul Mackerras
2009-10-29 6:55 ` Ingo Molnar
2009-10-29 6:55 ` Ingo Molnar
2009-10-30 6:04 ` Benjamin Herrenschmidt
2009-10-30 6:04 ` Benjamin Herrenschmidt
2009-11-08 9:35 ` Ingo Molnar
2009-11-08 9:35 ` Ingo Molnar
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=19177.352.47019.4942@drongo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--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 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.