Skip to contentSkip to conversation

tracing: use correct config guard CONFIG_STACK_TRACER

PATCH In review zhangwei(Jovi) 1 participant 1 message Jul 15, 2013 Tracing

lore
Share & tools
lore

zhangwei(Jovi)

author
#0 lore raw

PATCH 1/3 tracing: use correct config guard CONFIG_STACK_TRACER

We should use CONFIG_STACK_TRACER to guard readme text of stack tracer related file, not CONFIG_STACKTRACE.

Signed-off-by zhangwei(Jovi) <[email protected]>
---
 kernel/trace/trace.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
kernel/trace/trace.c +2 -2
index e71a8be..3d5a931 100644
@@ -3379,14 +3379,14 @@ static const char readme_msg[] =
 	"\n  snapshot\t\t- Like 'trace' but shows the content of the static snapshot buffer\n"
 	"\t\t\t  Read the contents for more information\n"
 #endif
-#ifdef CONFIG_STACKTRACE
+#ifdef CONFIG_STACK_TRACER
 	"  stack_trace\t\t- Shows the max stack trace when active\n"
 	"  stack_max_size\t- Shows current max stack size that was traced\n"
 	"\t\t\t  Write into this file to reset the max size (trigger a new trace)\n"
 #ifdef CONFIG_DYNAMIC_FTRACE
 	"  stack_trace_filter\t- Like set_ftrace_filter but limits what stack_trace traces\n"
 #endif
-#endif /* CONFIG_STACKTRACE */
+#endif /* CONFIG_STACK_TRACER */
 ;
 
 static ssize_t
Signature · 1 line
1.7.9.7