From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Matt Fleming <mjf@gentoo.org>,
linux-kernel@vger.kernel.org, Milton Miller <miltonm@bga.com>,
linuxppc-dev@ozlabs.org, Paul Mundt <lethal@linux-sh.org>,
Paul Mackerras <paulus@samba.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/5] powerpc: dynamic ftrace port
Date: Thu, 20 Nov 2008 20:20:09 +0100 [thread overview]
Message-ID: <20081120192009.GE3955@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0811201412230.3378@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 20 Nov 2008, Steven Rostedt wrote:
> >
> > 1) I removed the changes to recordmcount.pl. This is not a PowerPC
> > change, although PowerPC needs it for dynamic ftrace. But
> > the changes here can go via linux-tip.
>
> Ingo,
>
> I found that the recordmcount.pl change conflicts with a commit in
> linux-next, which is not in tip nor mainline. The commit is:
>
> 11ebca4a3f8337de2f4d1300bd307851d1191d53
> sh: dynamic ftrace support.
>
> Seems that this change came in through the sh repo. I have already
> resolved the conflicts with my updates for PowerPC with this commit.
> I can put this in a separate branch against linux-next if you like.
>
> I would like to get the changes to recordmcount.pl for PowerPC in
> linux-next soon, so I can also add a small clean up of this code.
> Jim Radfort has some updates as well for his port to arm.
Could you please extract the sh bits from 11ebca4a so that we can
apply it to tip/tracing/* standalone? It makes sense to carry it
without having the other bits of the SH changes.
It will collide in linux-next but it will be a same-content collision
with an easy enough (perhaps even automatic) resolution.
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@ozlabs.org, Milton Miller <miltonm@bga.com>,
Matt Fleming <mjf@gentoo.org>, Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCH 0/5] powerpc: dynamic ftrace port
Date: Thu, 20 Nov 2008 20:20:09 +0100 [thread overview]
Message-ID: <20081120192009.GE3955@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0811201412230.3378@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 20 Nov 2008, Steven Rostedt wrote:
> >
> > 1) I removed the changes to recordmcount.pl. This is not a PowerPC
> > change, although PowerPC needs it for dynamic ftrace. But
> > the changes here can go via linux-tip.
>
> Ingo,
>
> I found that the recordmcount.pl change conflicts with a commit in
> linux-next, which is not in tip nor mainline. The commit is:
>
> 11ebca4a3f8337de2f4d1300bd307851d1191d53
> sh: dynamic ftrace support.
>
> Seems that this change came in through the sh repo. I have already
> resolved the conflicts with my updates for PowerPC with this commit.
> I can put this in a separate branch against linux-next if you like.
>
> I would like to get the changes to recordmcount.pl for PowerPC in
> linux-next soon, so I can also add a small clean up of this code.
> Jim Radfort has some updates as well for his port to arm.
Could you please extract the sh bits from 11ebca4a so that we can
apply it to tip/tracing/* standalone? It makes sense to carry it
without having the other bits of the SH changes.
It will collide in linux-next but it will be a same-content collision
with an easy enough (perhaps even automatic) resolution.
Ingo
next prev parent reply other threads:[~2008-11-20 19:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 19:09 [PATCH 0/5] powerpc: dynamic ftrace port Steven Rostedt
2008-11-20 19:09 ` Steven Rostedt
2008-11-20 19:09 ` [PATCH 1/5] powerpc: ftrace, do not latency trace idle Steven Rostedt
2008-11-20 19:09 ` Steven Rostedt
2008-11-20 19:09 ` [PATCH 2/5] powerpc: ftrace, convert to new dynamic ftrace arch API Steven Rostedt
2008-11-20 19:09 ` Steven Rostedt
2008-11-24 1:43 ` Paul Mackerras
2008-11-24 1:43 ` Paul Mackerras
2008-11-24 2:49 ` Michael Ellerman
2008-11-24 2:49 ` Michael Ellerman
2008-11-24 18:00 ` Steven Rostedt
2008-11-24 18:00 ` Steven Rostedt
2008-11-20 19:09 ` [PATCH 3/5] powerpc: ftrace, use probe_kernel API to modify code Steven Rostedt
2008-11-20 19:09 ` Steven Rostedt
2008-11-20 19:09 ` [PATCH 4/5] powerpc/ppc64: ftrace, handle module trampolines for dyn ftrace Steven Rostedt
2008-11-20 19:09 ` Steven Rostedt
2008-11-24 2:26 ` Paul Mackerras
2008-11-24 2:26 ` Paul Mackerras
2008-11-24 17:56 ` Steven Rostedt
2008-11-24 17:56 ` Steven Rostedt
2008-11-24 20:59 ` Steven Rostedt
2008-11-24 20:59 ` Steven Rostedt
2008-11-20 19:09 ` [PATCH 5/5] powerpc/ppc32: ftrace, dynamic ftrace to handle modules Steven Rostedt
2008-11-20 19:09 ` Steven Rostedt
2008-11-24 2:35 ` Paul Mackerras
2008-11-24 2:35 ` Paul Mackerras
2008-11-20 19:15 ` [PATCH 0/5] powerpc: dynamic ftrace port Steven Rostedt
2008-11-20 19:15 ` Steven Rostedt
2008-11-20 19:20 ` Ingo Molnar [this message]
2008-11-20 19:20 ` Ingo Molnar
2008-11-20 19:16 ` Ingo Molnar
2008-11-20 19:16 ` Ingo Molnar
2008-11-20 19:24 ` Steven Rostedt
2008-11-20 19:24 ` Steven Rostedt
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=20081120192009.GE3955@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=mjf@gentoo.org \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.