[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081119092723.GC22309@elte.hu>
Date: Wed, 19 Nov 2008 10:27:23 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Paul Mackerras <paulus@...ba.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
linuxppc-dev@...abs.org
Subject: Re: [PATCH 0/7] Porting dynmaic ftrace to PowerPC
* Steven Rostedt <rostedt@...dmis.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.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists