From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: mingo@redhat.com, srostedt@redhat.com
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] trace: Fix some mistakes in error messages
Date: Tue, 12 Aug 2008 00:06:37 +0200 [thread overview]
Message-ID: <48A0B7ED.2010705@gmail.com> (raw)
This patch fixes some mistakes on the tracer in warning messages when
debugfs fails to create tracing files.
Kernel version: 2.6.27-rc1
Regards.
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
---
diff -rup a/kernel/trace/trace.c b/kernel/trace/trace.c
--- a/kernel/trace/trace.c 2008-08-11 22:44:25.000000000 +0200
+++ b/kernel/trace/trace.c 2008-08-11 23:10:39.000000000 +0200
@@ -2881,12 +2881,12 @@ static __init void tracer_init_debugfs(v
entry = debugfs_create_file("available_tracers", 0444, d_tracer,
&global_trace, &show_traces_fops);
if (!entry)
- pr_warning("Could not create debugfs 'trace' entry\n");
+ pr_warning("Could not create debugfs 'available_tracers' entry\n");
entry = debugfs_create_file("current_tracer", 0444, d_tracer,
&global_trace, &set_tracer_fops);
if (!entry)
- pr_warning("Could not create debugfs 'trace' entry\n");
+ pr_warning("Could not create debugfs 'current_tracer' entry\n");
entry = debugfs_create_file("tracing_max_latency", 0644, d_tracer,
&tracing_max_latency,
@@ -2899,7 +2899,7 @@ static __init void tracer_init_debugfs(v
&tracing_thresh, &tracing_max_lat_fops);
if (!entry)
pr_warning("Could not create debugfs "
- "'tracing_threash' entry\n");
+ "'tracing_thresh' entry\n");
entry = debugfs_create_file("README", 0644, d_tracer,
NULL, &tracing_readme_fops);
if (!entry)
@@ -2909,13 +2909,13 @@ static __init void tracer_init_debugfs(v
NULL, &tracing_pipe_fops);
if (!entry)
pr_warning("Could not create debugfs "
- "'tracing_threash' entry\n");
+ "'trace_pipe' entry\n");
entry = debugfs_create_file("trace_entries", 0644, d_tracer,
&global_trace, &tracing_entries_fops);
if (!entry)
pr_warning("Could not create debugfs "
- "'tracing_threash' entry\n");
+ "'trace_entries' entry\n");
#ifdef CONFIG_DYNAMIC_FTRACE
entry = debugfs_create_file("dyn_ftrace_total_info", 0444, d_tracer,
next reply other threads:[~2008-08-11 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 22:06 Frédéric Weisbecker [this message]
2008-08-14 13:13 ` [PATCH] trace: Fix some mistakes in error messages Frédéric Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2008-08-11 22:07 Frédéric Weisbecker
2008-08-15 12:59 ` Ingo Molnar
2008-08-15 19:08 ` Frédéric Weisbecker
2008-08-15 19:54 ` Ingo Molnar
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=48A0B7ED.2010705@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=srostedt@redhat.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