public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhaolei <zhaolei@cn.fujitsu.com>
To: Jiaying Zhang <jiayingz@google.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH 2/2] ftrace: Code cleanup for kernel/trace/trace_events_stage_*.h
Date: Wed, 08 Apr 2009 15:04:34 +0800	[thread overview]
Message-ID: <49DC4C82.40307@cn.fujitsu.com> (raw)
In-Reply-To: <5df78e1d0904072328v11e03131y5256d5c2ba9c03d@mail.gmail.com>

Jiaying Zhang wrote:
> Hi Steve,
> 
> I am looking at ftrace code more closely. It is also not clear to me why we
Hello, Zhang

Different people may have different taste on codeing style, but IMHO, separate
those complex definition into several files make me easy to understand.
It is only my personal code liking...

B.R.
Zhaolei

> want to define the trace event macros in three stage header files. I wonder
> whether it would be clearer if we merge them together. Then people don't
> need to look at three files to understand what is going on in event tracing.
> 
> Jiaying
> 
> On Mon, Apr 6, 2009 at 6:54 PM, Steven Rostedt <rostedt@goodmis.org
> <mailto:rostedt@goodmis.org>> wrote:
> 
> 
>     On Fri, 3 Apr 2009, Zhaolei wrote:
> 
>     > Add TRACE_FORMAT's define for trace_events_stage_2.h.
>     > Although it is already defined in trace_events_stage_1.h, we
>     should make each
>     > function independence.
>     >
>     > Move TP_fast_assign's define from trace_events_stage_2.h to
>     > trace_events_stage_3.h because it is used there.
>     >
>     > Unify TRACE_EVENT's 5th argument's name to "assign"
>     >
>     > Impact: cleanup, no functionality changed
>     >
>     > Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com
>     <mailto:zhaolei@cn.fujitsu.com>>
> 
>     I see what you are doing here, but I'm a little hesitant to apply it.
>     I'm getting ready to travel, so I do not have the time to look deeper at
>     this today. I'll try to do it while I'm traveling.
> 
>     Thanks,
> 
>     -- Steve
>     --
>     To unsubscribe from this list: send the line "unsubscribe
>     linux-kernel" in
>     the body of a message to majordomo@vger.kernel.org
>     <mailto:majordomo@vger.kernel.org>
>     More majordomo info at  http://vger.kernel.org/majordomo-info.html
>     Please read the FAQ at  http://www.tux.org/lkml/
> 
> 



  parent reply	other threads:[~2009-04-08  7:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 10:24 [PATCH 1/2] ftrace: Correct a text align for event format output Zhaolei
2009-04-03 10:26 ` [PATCH 2/2] ftrace: Code cleanup for kernel/trace/trace_events_stage_*.h Zhaolei
2009-04-07  1:54   ` Steven Rostedt
2009-04-08  7:04     ` Jiaying Zhang
     [not found]     ` <5df78e1d0904072328v11e03131y5256d5c2ba9c03d@mail.gmail.com>
2009-04-08  7:04       ` Zhaolei [this message]
2009-04-08  7:16         ` Jiaying Zhang
2009-04-16 14:55     ` Steven Rostedt
2009-04-17  0:31       ` Zhaolei
2009-04-07  1:50 ` [PATCH 1/2] ftrace: Correct a text align for event format output Steven Rostedt
2009-04-07 13:13 ` [tip:tracing/urgent] " Zhaolei

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=49DC4C82.40307@cn.fujitsu.com \
    --to=zhaolei@cn.fujitsu.com \
    --cc=jiayingz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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