From: Li Zefan <lizf@cn.fujitsu.com>
To: rostedt@goodmis.org
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Tom Zanussi <tzanussi@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH v2] tracing: Clean up trace.h
Date: Thu, 10 Sep 2009 10:25:43 +0800 [thread overview]
Message-ID: <4AA863A7.5030909@cn.fujitsu.com> (raw)
In-Reply-To: <1252549061.18996.3.camel@gandalf.stny.rr.com>
于 2009年09月10日 10:17, Steven Rostedt 写道:
> On Thu, 2009-09-10 at 09:34 +0800, Li Zefan wrote:
>> - remove some dead code
>> - remove @stats from struct tracer
>> - move DEFINE_COMPARISON_PRED() and DEFINE_EQUALITY_PRED()
>> to kernel/trace/trace_events_filter.c
>>
>
> Actually, Li if you don't mind, I'm going to break this up into separate
> patches. Each of the above "topics" really should be a separate patch.
> It makes bisecting and such nicer if for some strange reason this patch
> became the cause.
>
Actually it does more than I described:
- indent some lines
- fix a typo in comment
- remove trace_field_cont
- remove tracer_switch_ops
- remove @stats from struct tracer
- move 2 macros to trace_events_filter.c
I'm not sure it worths breaking into several patches, since each of them
is trivial.
But I won't mind if you break this up, or if you want me to do
this.
next prev parent reply other threads:[~2009-09-10 2:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 1:34 [PATCH v2] tracing: Clean up trace.h Li Zefan
2009-09-10 1:43 ` Frederic Weisbecker
2009-09-10 2:17 ` Steven Rostedt
2009-09-10 2:25 ` Li Zefan [this message]
2009-09-10 13:34 ` Steven Rostedt
2009-09-12 7:52 ` [tip:tracing/core] tracing: remove dead code tip-bot for Li Zefan
2009-09-12 7:52 ` [tip:tracing/core] tracing: format clean ups tip-bot for Li Zefan
2009-09-12 7:53 ` [tip:tracing/core] tracing: remove stats from struct tracer tip-bot for Li Zefan
2009-09-12 7:53 ` [tip:tracing/core] tracing: move PRED macros to trace_events_filter.c tip-bot for Li Zefan
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=4AA863A7.5030909@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.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