From: Dmitry Safonov <0x7f454c46@gmail.com>
To: rostedt@goodmis.org, mingo@redhat.com
Cc: linux-kernel@vger.kernel.org, Dmitry Safonov <0x7f454c46@gmail.com>
Subject: [PATCH] trace_functions_graph: Remove __trace_graph_function
Date: Fri, 30 Oct 2015 22:18:23 +0300 [thread overview]
Message-ID: <1446232703-13164-1-git-send-email-0x7f454c46@gmail.com> (raw)
In-Reply-To: <1446232038-27113-1-git-send-email-0x7f454c46@gmail.com>
__trace_graph_funciton is used in only one location, and is static.
As it's small function there is no need to keep it separated out.
Signed-off-by: Dmitry Safonov <0x7f454c46@gmail.com>
---
kernel/trace/trace_functions_graph.c | 14 +++-----------
1 file changed, 3 insertions(+), 11 deletions(-)
diff --git a/kernel/trace/trace_functions_graph.c b/kernel/trace/trace_functions_graph.c
index ca98445782acaa..dc45caefe4b1ac 100644
--- a/kernel/trace/trace_functions_graph.c
+++ b/kernel/trace/trace_functions_graph.c
@@ -360,9 +360,9 @@ static int trace_graph_thresh_entry(struct ftrace_graph_ent *trace)
return trace_graph_entry(trace);
}
-static void
-__trace_graph_function(struct trace_array *tr,
- unsigned long ip, unsigned long flags, int pc)
+void trace_graph_function(struct trace_array *tr,
+ unsigned long ip, unsigned long parent_ip,
+ unsigned long flags, int pc)
{
u64 time = trace_clock_local();
struct ftrace_graph_ent ent = {
@@ -380,14 +380,6 @@ __trace_graph_function(struct trace_array *tr,
__trace_graph_return(tr, &ret, flags, pc);
}
-void
-trace_graph_function(struct trace_array *tr,
- unsigned long ip, unsigned long parent_ip,
- unsigned long flags, int pc)
-{
- __trace_graph_function(tr, ip, flags, pc);
-}
-
void __trace_graph_return(struct trace_array *tr,
struct ftrace_graph_ret *trace,
unsigned long flags,
--
2.6.1
next prev parent reply other threads:[~2015-10-30 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 19:07 Dmitry Safonov
2015-10-30 19:18 ` Dmitry Safonov [this message]
2015-10-30 19:19 ` Dmitry Safonov
2015-10-30 19:18 ` kbuild test robot
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=1446232703-13164-1-git-send-email-0x7f454c46@gmail.com \
--to=0x7f454c46@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
all inboxes | Powered by JetHome®