tracing: Have HIST_TRIGGERS select TRACING
PATCH 1/1 tracing: Have HIST_TRIGGERS select TRACING
The kbuild test robot reported a compile error if HIST_TRIGGERS was enabled but nothing else that selected TRACING was configured in.
HIST_TRIGGERS should directly select it and not rely on anything else to do it.
Signed-off-by Tom Zanussi <[email protected]>
--- kernel/trace/Kconfig | 1 + 1 file changed, 1 insertion(+)
kernel/trace/Kconfig +1 -0
@@ -542,6 +542,7 @@ config HIST_TRIGGERS bool "Histogram triggers" depends on ARCH_HAVE_NMI_SAFE_CMPXCHG select TRACING_MAP + select TRACING default n help Hist triggers allow one or more arbitrary trace event fields
Signature · 1 line
1.9.3
Steven Rostedt
maintainerQuoted 6 lines · On Sun, 03 Jul 2016 08:51:34 -0500 Tom Zanussi <[email protected]>…
The kbuild test robot reported a compile error if
HIST_TRIGGERSwas enabled but nothing else that selected TRACING was configured in.
HIST_TRIGGERSshould directly select it and not rely on anything else to do it.
I added:
Reported-by kbuild test robot <[email protected]>
Fixes 7ef224d1d0e3a ("tracing: Add 'hist' event trigger command")
This isn't that big of a deal, so I'm just going to put it into my queue for the next merge window.
-- Steve
Quoted 17 lines
Signed-off-by Tom Zanussi <[email protected]>--- kernel/trace/Kconfig | 1 + 1 file changed, 1 insertion(+)kernel/trace/Kconfig +1
-0@@ -542,6 +542,7 @@ config HIST_TRIGGERS bool "Histogram triggers" depends on ARCH_HAVE_NMI_SAFE_CMPXCHG select TRACING_MAP + select TRACING default n help Hist triggers allow one or more arbitrary trace event fields