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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090824112910.GA18752@linux-sh.org>
Date:	Mon, 24 Aug 2009 20:29:10 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Josh Stone <jistone@...hat.com>, linux-kernel@...r.kernel.org,
	Jason Baron <jbaron@...hat.com>,
	Li Zefan <lizf@...fujitsu.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Jiaying Zhang <jiayingz@...gle.com>,
	Martin Bligh <mbligh@...gle.com>,
	Lai Jiangshan <laijs@...fujitsu.com>
Subject: Re: [PATCH v3 1/4] tracing: Rename TIF_SYSCALL_FTRACE->_TRACEPOINT

On Mon, Aug 24, 2009 at 01:24:26PM +0200, Ingo Molnar wrote:
> * Frederic Weisbecker <fweisbec@...il.com> wrote:
> > On Mon, Aug 24, 2009 at 10:42:45AM +0200, Ingo Molnar wrote:
> > > 
> > > * Frederic Weisbecker <fweisbec@...il.com> 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@...ux-sh.org> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/