From: Ingo Molnar <mingo@elte.hu>
To: Zhaolei <zhaolei@cn.fujitsu.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ftrace: Output REC->var instead of __entry->varfor trace format
Date: Fri, 10 Apr 2009 15:46:43 +0200 [thread overview]
Message-ID: <20090410134643.GA24809@elte.hu> (raw)
In-Reply-To: <2EAA5B9CE11E4D62AB83F83D5CB25C17@zhaoleiwin>
* Zhaolei <zhaolei@cn.fujitsu.com> wrote:
> * From: "Ingo Molnar" <mingo@elte.hu>
> >
> > * Zhaolei <zhaolei@cn.fujitsu.com> wrote:
> >
> >> print fmt: "irq=%d return=%s", __entry->irq, __entry->ret ? \"handled\" : \"unhandled\"
> >>
> >> "__entry" should be convert to "REC" by __stringify() macro.
> >>
> >> Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> >> ---
> >> kernel/trace/trace_events_stage_2.h | 4 ++--
> >> 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > good fix, but it is causing build trouble when applied to latest
> > tip/master:
> >
> > include/trace/sched_event_types.h:257:1: error: macro "__stringify"
> > passed 3 arguments, but takes just 1
> Hello, Ingo
>
> I tested this patch before send, but haven't see this error. env
> is: gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)
>
> This patch need on top of my previous one: [PATCH 1/2] Make
> __stringify support variable argument macro Maybe this is the
> reason.
ah, indeed - i missed the 1/2 patch. I'll have another look.
Ingo
next prev parent reply other threads:[~2009-04-10 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 8:58 [PATCH 1/2] Make __stringify support variable argument macro Zhaolei
2009-04-08 9:00 ` [PATCH 2/2] ftrace: Output REC->var instead of __entry->var for trace format Zhaolei
2009-04-08 11:29 ` Frederic Weisbecker
2009-04-08 11:31 ` Frederic Weisbecker
2009-04-08 12:06 ` Ingo Molnar
2009-04-09 0:45 ` [PATCH 2/2] ftrace: Output REC->var instead of __entry->varfor " Zhaolei
2009-04-10 13:46 ` Ingo Molnar [this message]
2009-04-10 14:06 ` [tip:tracing/urgent] ftrace: Output REC->var instead of __entry->var for " Zhaolei
2009-04-10 14:06 ` [tip:tracing/urgent] Make __stringify support variable argument macros too 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=20090410134643.GA24809@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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