Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 991821c8 authored by zhangwei(Jovi)'s avatar zhangwei(Jovi) Committed by Steven Rostedt
Browse files

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.

Link: http://lkml.kernel.org/r/51E3B3A2.8080609@huawei.com



Signed-off-by: default avatarzhangwei(Jovi) <jovi.zhangwei@huawei.com>
Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
parent ad81f054

kernel/trace/trace.c

+2 −2
Original line number Diff line number Diff line
@@ -3537,14 +3537,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