Re: [PATCH v3 1/4] tracing: Rename TIF_SYSCALL_FTRACE->_TRACEPOINT

[Paul Mundt]

On Mon, Aug 24, 2009 at 01:24:26PM +0200, Ingo Molnar wrote:
> * Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote:
> > On Mon, Aug 24, 2009 at 10:42:45AM +0200, Ingo Molnar wrote:
> > > 
> > > * Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote:
> > > 
> > > > On Fri, Aug 21, 2009 at 09:58:42PM -0700, Josh Stone wrote:
> > > >
> > > > > This thread flag is no longer specific to just ftrace, so 
> > > > > TIF_SYSCALL_TRACEPOINT may be a more apt name.
> > > > 
> > > > Adding Paul Mundt <lethal@xxxxxxxxxxxx> in Cc, the sh tree also 
> > > > has the syscalls tracing support (in a seperate branch).
> > > 
> > > Btw., is there an URI for that separate branch?
> > > 
> > > 	Ingo
> > 
> > I guess it's:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6.git \
> > 	sh/ftrace
> 
> ok, i checked - this is not a pure topical tree, it's intermingled 
> with other SH changes, so it cannot be pulled into the tracing tree.
> 
> Obviously only such trees can be pulled into the tracing tree that 
> limit their role to tracing and are non-rebasing.
> 
Yes, post-2.6.32 merge window I'll keep the sh/ftrace branch isolated
from the rest of the sh changes, at which point it should be possible to
pull in to -tip directly. I generally do not rebase topic branches.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/