linux-kernel - Re: [GIT PULL v2][PATCH 0/10] tracing/core: various fixes

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] [day] [month] [year] [list]

Message-ID: <20090526222251.GH5969@nowhere>
Date:	Wed, 27 May 2009 00:22:52 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Li Zefan <lizf@...fujitsu.com>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Zhaolei <zhaolei@...fujitsu.com>,
	Tom Zanussi <tzanussi@...il.com>
Subject: Re: [GIT PULL v2][PATCH 0/10] tracing/core: various fixes

On Tue, May 26, 2009 at 05:30:43PM -0400, Steven Rostedt wrote:
> 
> On Tue, 26 May 2009, Frederic Weisbecker wrote:
> > Steven Rostedt (5):
> >       tracing: add __print_flags for events
> >       tracing: add previous task state info to sched switch event
> >       tracing: add flag output for kmem events
> >       tracing: add __print_symbolic to trace events
> >       tracing: convert irq events to use __print_symbolic
> > 
> > Zhaolei (2):
> >       ftrace: Add task_comm support for trace_event
> >       ftrace: clean up of using ftrace_event_enable_disable()
> 
> BTW, these are in tip/tracing/ftrace :-/


Yes. I prepared the first request against tracing/core
and have discovered today what was in tracing/ftrace :)

But Zhaolei's patches are not the same. The v1 is on
tracing/ftrace, it doesn't contain the fix for the build
error. Then Ingo suggested me to cherry-pick the missing
patches in tracing/core from tracing/ftrace. And here came
the second pull request.

So, may be I should send a new request containing the last
fixes but against tracing/ftrace. So that we'll have
the same result without the kconfig tricks that solve the
build error.

Hm?

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