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>

diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index e0cea282e0c58e8f37c7a8aedadfdfd8452ac60c..b58f43bec3636e050bc6129d1fa58341aac1c946 100644 (file)
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -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"