public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: mingo@redhat.com, srostedt@redhat.com,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] trace: Fix some mistakes in error messages
Date: Fri, 15 Aug 2008 21:08:22 +0200	[thread overview]
Message-ID: <48A5D426.20703@gmail.com> (raw)
In-Reply-To: <20080815125937.GB30597@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

Ingo Molnar a écrit :
> * Frédéric Weisbecker <fweisbec@gmail.com> wrote:
> 
>> This patch fixes some mistakes on the tracer in warning messages when 
>> debugfs fails to create tracing files. Kernel version: 2.6.27-rc1
> 
> hm, the patch is nice, but it is whitespace damaged. Please resend along 
> the lines of Documentation/email-clients.txt, or as an attachment.
> 
> 	Ingo


Sorry. Now it should be correct.

Pach V2
-------

This patch fixes some mistakes on the tracer in warning messages when 
debugfs fails to create tracing files.

Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
---


[-- Attachment #2: resend_debugfs_warns.diff --]
[-- Type: text/x-patch, Size: 1745 bytes --]

diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 8f3fb3d..943f278 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -2881,12 +2881,12 @@ static __init void tracer_init_debugfs(void)
 	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(void)
 				    &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(void)
 				    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,

  reply	other threads:[~2008-08-15 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 22:07 [PATCH] trace: Fix some mistakes in error messages Frédéric Weisbecker
2008-08-15 12:59 ` Ingo Molnar
2008-08-15 19:08   ` Frédéric Weisbecker [this message]
2008-08-15 19:54     ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2008-08-11 22:06 Frédéric Weisbecker
2008-08-14 13:13 ` Frédéric 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=48A5D426.20703@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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