From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <srostedt@redhat.com>
Subject: [PATCH 3/3] ftrace: rename the ftrace tracer to function
Date: Mon, 06 Oct 2008 19:06:13 -0400 [thread overview]
Message-ID: <20081006231149.438702200@goodmis.org> (raw)
In-Reply-To: <20081006230610.024517480@goodmis.org>
[-- Attachment #1: ftrace-rename-function-trace.patch --]
[-- Type: text/plain, Size: 1047 bytes --]
To avoid further confusion between the ftrace infrastructure and the
function tracer. This patch renames the "ftrace" function tracer
to "function".
Now in available_tracers, instead of "ftrace" there will be "function".
This makes more sense, since people will not know exactly what the
"ftrace" tracer does.
Signed-off-by: Steven Rostedt <srostedt@redhat.com>
---
kernel/trace/trace_functions.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-tip.git/kernel/trace/trace_functions.c
===================================================================
--- linux-tip.git.orig/kernel/trace/trace_functions.c 2008-10-06 18:50:38.000000000 -0400
+++ linux-tip.git/kernel/trace/trace_functions.c 2008-10-06 18:51:09.000000000 -0400
@@ -64,7 +64,7 @@ static void function_trace_ctrl_update(s
static struct tracer function_trace __read_mostly =
{
- .name = "ftrace",
+ .name = "function",
.init = function_trace_init,
.reset = function_trace_reset,
.ctrl_update = function_trace_ctrl_update,
--
next prev parent reply other threads:[~2008-10-06 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 23:06 [PATCH 0/3] ftrace: separate ftrace from ftrace Steven Rostedt
2008-10-06 23:06 ` [PATCH 1/3] ftrace: fix depends Steven Rostedt
2008-10-06 23:06 ` [PATCH 2/3] ftrace: rename FTRACE to FUNCTION_TRACER Steven Rostedt
2008-10-06 23:06 ` Steven Rostedt [this message]
2008-10-20 16:31 ` [PATCH 0/3] ftrace: separate ftrace from ftrace 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=20081006231149.438702200@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
Powered by JetHome