tracing: clean up tracepoints kconfig structure

do not expose users to CONFIG_TRACEPOINTS - tracers can select it
just fine.

update ftrace to select CONFIG_TRACEPOINTS.

Signed-off-by: Ingo Molnar <mingo@elte.hu>

2 files changed, 6 insertions, 4 deletions

diff --git a/init/Kconfig b/init/Kconfig
index d5994490b0b0..031344f954fd 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -771,11 +771,12 @@ config PROFILING
           Say Y here to enable the extended profiling support mechanisms used
           by profilers such as OProfile.
 
+#
+# Place an empty function call at each tracepoint site. Can be
+# dynamically changed for a probe function.
+#
 config TRACEPOINTS
-        bool "Activate tracepoints"
-        help
-          Place an empty function call at each tracepoint site. Can be
-          dynamically changed for a probe function.
+        bool
 
 config MARKERS
         bool "Activate markers"
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 263e9e6bbd60..cae2637d5e68 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -14,6 +14,7 @@ config TRACING
         bool
         select DEBUG_FS
         select STACKTRACE
+        select TRACEPOINTS
 
 config FTRACE
         bool "Kernel Function Tracer"