From: Steven Rostedt <rostedt@goodmis.org>
To: Joe Perches <joe@perches.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ftrace.h: TP_fast_assign - use do {} while (0);
Date: Wed, 09 Sep 2009 12:58:05 -0400 [thread overview]
Message-ID: <1252515485.27001.25.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1252514933.28130.45.camel@Joe-Laptop.home>
On Wed, 2009-09-09 at 09:48 -0700, Joe Perches wrote:
> Perhaps this is a more kernel style standard way to allow
> local variables in TP_fast_assign.
>
> http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commitdiff;h=a9c1c3abe1160a5632e48c929b02b740556bf423
>
> Signed-off-by: Joe Perches <joe@perches.com>
>
> diff --git a/include/trace/ftrace.h b/include/trace/ftrace.h
> index f64fbaa..4c99bdc 100644
> --- a/include/trace/ftrace.h
> +++ b/include/trace/ftrace.h
> @@ -142,7 +142,7 @@
> #define TP_printk(fmt, args...) "%s, %s\n", #fmt, __stringify(args)
>
> #undef TP_fast_assign
> -#define TP_fast_assign(args...) args
> +#define TP_fast_assign(args...) do { args } while (0);
>
> #undef TP_perf_assign
> #define TP_perf_assign(args...)
This is not a normal macro that is used globally. I like the referenced
commit better, because it shows where it is used what is happening.
Note, TP_fast_assign is just a parameter into another macro, and using
do { } while (0) is not really going to help change anything. This
doesn't even remove a checkpatch warning.
-- Steve
prev parent reply other threads:[~2009-09-09 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 16:48 Joe Perches
2009-09-09 16:58 ` Steven Rostedt [this message]
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=1252515485.27001.25.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@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
all inboxes | Powered by JetHome®