lkml.org 
[lkml]   [2016]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 4.7 091/141] tracing: Have HIST_TRIGGERS select TRACING
    Date
    4.7-stable review patch.  If anyone has any objections, please let me know.

    ------------------

    From: Tom Zanussi <tom.zanussi@linux.intel.com>

    commit 7ad8fb61c4abf589596f0a4da34d987471481569 upstream.

    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.

    Link: http://lkml.kernel.org/r/57791866.8080505@linux.intel.com

    Reported-by: kbuild test robot <fennguang.wu@intel.com>
    Fixes: 7ef224d1d0e3a ("tracing: Add 'hist' event trigger command")
    Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    ---
    kernel/trace/Kconfig | 1 +
    1 file changed, 1 insertion(+)

    --- a/kernel/trace/Kconfig
    +++ b/kernel/trace/Kconfig
    @@ -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

    \
     
     \ /
      Last update: 2016-10-06 11:29    [W:4.095 / U:0.036 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site