linux-kernel - Re: [PATCH 4/5 v3] tracing/core: drop the old ftrace_printk implementation in favour of 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]

Date:	Fri, 6 Mar 2009 13:04:00 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 4/5 v3] tracing/core: drop the old ftrace_printk
 implementation in favour of ftrace_bprintk


On Fri, 6 Mar 2009, Ingo Molnar wrote:
> > 
> > i've put them into a separate branch forked off 
> > tip:tracing/ftrace: tip:tracing/printk. The two vsprintf 
> > patches are in tip:core/printk and merged into tracing/ftrace.
> > 
> > You can thus apply your current enhancements without any 
> > interaction with me - and merge tracing/printk into the 
> > tip:tracing/ftrace branch on your own schedule, ok?
> 
> ah - i misunderstood - i see that it interacts with your commits 
> from last night.
> 
> I've excluded tip:tracing/printk from tip:master for now and 
> will let you guys fix it up when you have time for it.

Ingo,

It compiles fine. Only a new item in the struct was added, nothing was 
removed. It just prints out a bit funny ;-)

You can go ahead and merge it into tracing/ftrace, and then I can work 
with that to fix up the formatting.

-- Steve

--
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/