From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Li Zefan <lizf@cn.fujitsu.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Zhaolei <zhaolei@cn.fujitsu.com>,
Tom Zanussi <tzanussi@gmail.com>
Subject: Re: [GIT PULL v2][PATCH 0/10] tracing/core: various fixes
Date: Wed, 27 May 2009 00:22:52 +0200 [thread overview]
Message-ID: <20090526222251.GH5969@nowhere> (raw)
In-Reply-To: <alpine.DEB.2.00.0905261730180.26705@gandalf.stny.rr.com>
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?
next prev parent reply other threads:[~2009-05-26 22:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 2:04 [PATCH 0/5] tracing/core: various fixes Frederic Weisbecker
2009-05-26 2:04 ` [PATCH 1/5] tracing: add trace_event_read_lock() Frederic Weisbecker
2009-05-26 2:04 ` [PATCH 2/5] tracing/events: change the type of __str_loc_item to unsigned short Frederic Weisbecker
2009-05-26 2:04 ` [PATCH 3/5] kmemtrace: fix kernel parameter documentation Frederic Weisbecker
2009-05-26 2:04 ` [PATCH 4/5] ftrace: Add task_comm support for trace_event Frederic Weisbecker
2009-05-26 2:04 ` [PATCH 5/5] ftrace: clean up of using ftrace_event_enable_disable() Frederic Weisbecker
2009-05-26 18:55 ` [GIT PULL v2][PATCH 0/10] tracing/core: various fixes Frederic Weisbecker
2009-05-26 21:30 ` Steven Rostedt
2009-05-26 22:22 ` Frederic Weisbecker [this message]
2009-05-26 19:46 ` [PATCH 0/5] " Steven Rostedt
2009-05-26 20:06 ` Frederic Weisbecker
2009-05-26 21:10 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090526222251.GH5969@nowhere \
--to=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
--cc=zhaolei@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox