From: Paul Mackerras <paulus@samba.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/7] Porting dynmaic ftrace to PowerPC
Date: Wed, 19 Nov 2008 21:38:26 +1100 [thread overview]
Message-ID: <18723.60578.179210.736789@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20081119092723.GC22309@elte.hu>
Ingo Molnar writes:
> * Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Wed, 19 Nov 2008, Paul Mackerras wrote:
> >
> > > Steven Rostedt writes:
> > >
> > > > Can I add your Acked-by: to all these patches that I submitted? I'm going
> > > > to recommit them with a consistent subject (all lower case ppc), but I'm
> > > > not going to change the patches themselves.
> > > >
> > > > Would you two be fine with that? Or at least one of you?
> > >
> > > My preference would be for the patches to go through the powerpc tree
> > > unless there is a good reason for them to go via another tree.
> >
> > I have no problem with that. The only thing is that we have a lot of
> > pending work still in the linux-tip tree, which you may need to pull
> > in to get these patches working. Well, there's two or three commits
> > in the generic code that I know the PPC code is dependent on.
> >
> > I could give you a list of commits in tip that need to go mainline
> > first before we can pull in the PPC changes. Then you could wait
> > till those changes make it into 29 and then you could push the PPC
> > modifications in from your tree.
>
> note that this inserts a lot of (unnecessary) serialization and a
> window of non-testing - by all likelyhood this will delay ppc ftrace
> to v2.6.30 or later kernels.
Well, note that I said "unless there is a good reason". If it does
need to go via your tree, it can, though I don't see that it will get
much testing on powerpc there, and having it there will make it harder
to manage any conflicts with the other stuff I have queued up.
How much generic stuff that's not upstream do the powerpc ftrace
patches depend on?
Paul.
next prev parent reply other threads:[~2008-11-19 10:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 21:24 Steven Rostedt
2008-11-16 21:24 ` [PATCH 1/7] ftrace, PPC: do not latency trace idle Steven Rostedt
2008-11-17 3:43 ` Paul Mackerras
2008-11-17 15:43 ` Steven Rostedt
2008-11-16 21:24 ` [PATCH 2/7] ftrace, ppc: convert to new dynamic ftrace arch API Steven Rostedt
2008-11-17 3:57 ` Paul Mackerras
2008-11-17 15:47 ` Steven Rostedt
2008-11-16 21:24 ` [PATCH 3/7] ftrace: powerpc mcount record port Steven Rostedt
2008-11-16 21:24 ` [PATCH 4/7] ftrace, PPC: use probe_kernel API to modify code Steven Rostedt
2008-11-17 4:44 ` Paul Mackerras
2008-11-17 15:51 ` Steven Rostedt
2008-11-16 21:24 ` [PATCH 5/7] ftrace, PPC64: handle module trampolines for dyn ftrace Steven Rostedt
2008-11-17 5:00 ` Paul Mackerras
2008-11-17 16:02 ` Steven Rostedt
2008-11-17 16:18 ` Steven Rostedt
2008-11-16 21:24 ` [PATCH 6/7] ftrace,ppc32: enabled dynamic ftrace Steven Rostedt
2008-11-16 21:24 ` [PATCH 7/7] ftrace,ppc32: dynamic ftrace to handle modules Steven Rostedt
2008-11-16 22:55 ` [PATCH 0/7] Porting dynmaic ftrace to PowerPC Paul Mackerras
2008-11-17 15:42 ` Steven Rostedt
2008-11-17 20:03 ` Steven Rostedt
2008-11-18 13:56 ` Steven Rostedt
2008-11-19 2:38 ` Paul Mackerras
2008-11-19 3:04 ` Steven Rostedt
2008-11-19 9:27 ` Ingo Molnar
2008-11-19 10:38 ` Paul Mackerras [this message]
2008-11-19 10:57 ` Ingo Molnar
2008-11-19 11:35 ` Paul Mackerras
2008-11-19 12:10 ` Steven Rostedt
2008-11-19 12:15 ` 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=18723.60578.179210.736789@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®