forked from Minki/linux
ftrace: fix trace_nop config select
Impact: build fix on non-function-tracing architectures The trace_nop is the tracer that is defined when no tracer is set in the ftrace infrastructure. The trace_nop was mistakenly selected by HAVE_FTRACE due to the confusion between ftrace infrastructure and the ftrace function tracer (which has been solved by renaming the function tracer). This patch changes the select to the approriate TRACING. This patch should fix compile errors on architectures that do not define the FUNCTION_TRACER. Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
parent
0b6e4d56bf
commit
f3384b28a0
@ -8,7 +8,6 @@ config NOP_TRACER
|
||||
|
||||
config HAVE_FUNCTION_TRACER
|
||||
bool
|
||||
select NOP_TRACER
|
||||
|
||||
config HAVE_DYNAMIC_FTRACE
|
||||
bool
|
||||
@ -28,6 +27,7 @@ config TRACING
|
||||
select RING_BUFFER
|
||||
select STACKTRACE
|
||||
select TRACEPOINTS
|
||||
select NOP_TRACER
|
||||
|
||||
menu "Tracers"
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user