From: tip-bot for Joe Perches <joe@perches.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
fweisbec@gmail.com, joe@perches.com, rostedt@goodmis.org,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:tracing/urgent] ftrace.h: Use common pr_info fmt string
Date: Sun, 13 Dec 2009 07:37:15 GMT [thread overview]
Message-ID: <tip-4819568f23a8bef0ca99b740ca60fe2450ab0aac@git.kernel.org> (raw)
In-Reply-To: <1260651974.2637.4.camel@Joe-Laptop.home>
Commit-ID: 4819568f23a8bef0ca99b740ca60fe2450ab0aac
Gitweb: http://git.kernel.org/tip/4819568f23a8bef0ca99b740ca60fe2450ab0aac
Author: Joe Perches <joe@perches.com>
AuthorDate: Sat, 12 Dec 2009 13:06:13 -0800
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Sun, 13 Dec 2009 08:14:45 +0100
ftrace.h: Use common pr_info fmt string
Reduces fmt string space a bit.
Signed-off-by: Joe Perches <joe@perches.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
LKML-Reference: <1260651974.2637.4.camel@Joe-Laptop.home>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
include/trace/ftrace.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/trace/ftrace.h b/include/trace/ftrace.h
index d1b3de9..c4eca38 100644
--- a/include/trace/ftrace.h
+++ b/include/trace/ftrace.h
@@ -733,7 +733,7 @@ static int ftrace_raw_reg_event_##call(struct ftrace_event_call *unused)\
ret = register_trace_##call(ftrace_raw_event_##call); \
if (ret) \
pr_info("event trace: Could not activate trace point " \
- "probe to " #call "\n"); \
+ "probe to %s\n", #call); \
return ret; \
} \
\
next prev parent reply other threads:[~2009-12-13 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-12 21:06 [PATCH] ftrace.h: Use common pr_info fmt string Joe Perches
2009-12-13 7:37 ` tip-bot for Joe Perches [this message]
[not found] ` <1260715695.2146.412.camel@gandalf.stny.rr.com>
2009-12-13 14:50 ` [tip:tracing/urgent] " Frederic Weisbecker
2009-12-13 17:53 ` Joe Perches
2009-12-13 18:33 ` Joe Perches
2009-12-13 21:24 ` Frederic Weisbecker
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=tip-4819568f23a8bef0ca99b740ca60fe2450ab0aac@git.kernel.org \
--to=joe@perches.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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