__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 <[email protected]> --- kernel/trace/trace_functions_graph.c | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/kernel/trace/trace_functions_graph.c b/kernel/trace/trace_functions_graph.c index ca98445782acaa..db434d2a9d6243 100644 --- a/kernel/trace/trace_functions_graph.c +++ b/kernel/trace/trace_functions_graph.c @@ -360,8 +360,7 @@ 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, +void trace_graph_function(struct trace_array *tr, unsigned long ip, unsigned long flags, int pc) { u64 time = trace_clock_local(); @@ -380,14 +379,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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
