From: Joe Perches <joe@perches.com>
To: Jovi Zhang <bookjovi@gmail.com>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Ingo Molnar" <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ftrace: using pr_fmt for better printk output
Date: Mon, 16 Jul 2012 22:29:17 -0700 [thread overview]
Message-ID: <1342502957.8377.125.camel@joe2Laptop> (raw)
In-Reply-To: <CACV3sb+EoHPqM7ih-5HpiT-o9CqobhaiJJ3E7-8H7N=tR7URig@mail.gmail.com>
On Tue, 2012-07-17 at 13:23 +0800, Jovi Zhang wrote:
> I don't make sure if there have some method or skill to let GCC knows
> subsystem name automatically,
> use built-in macro __FILE__? but this need condition of subsystem name
> is same as file name,
> not so easily to guarantee that.
You could use KBUILD_BASENAME instead.
prev parent reply other threads:[~2012-07-17 5:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 1:15 [PATCH] ftrace: using pr_fmt for better printk output Jovi Zhang
2012-07-17 3:42 ` Joe Perches
2012-07-17 4:25 ` Steven Rostedt
2012-07-17 5:07 ` Joe Perches
2012-07-17 5:32 ` Jovi Zhang
2012-07-17 5:37 ` Joe Perches
2012-07-17 6:47 ` Jovi Zhang
2012-07-17 5:23 ` Jovi Zhang
2012-07-17 5:27 ` Joe Perches
2012-07-17 5:29 ` Joe Perches [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=1342502957.8377.125.camel@joe2Laptop \
--to=joe@perches.com \
--cc=bookjovi@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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