[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFDyS3PY=qpegLLk+yKiieNH-No-Khqtbv15o8hHHaHzfcx6Uw@mail.gmail.com>
Date: Wed, 23 Sep 2015 17:54:26 +0300
From: Tal Shorer <tal.shorer@...il.com>
To: Tal Shorer <tal.shorer@...il.com>,
Steven Rostedt <rostedt@...dmis.org>
Cc: mingo@...hat.com,
"<linux-kernel@...r.kernel.org>" <linux-kernel@...r.kernel.org>
Subject: Re: [Patch v3 2/2] tracing: gpio: add Kconfig option for
enabling/disabling trace events
Merge window for 4.3 is over, so I figured I might bring this back up
On Tue, Aug 11, 2015 at 10:45 PM, Tal Shorer <tal.shorer@...il.com> wrote:
> ping?
>
> On Sat, Aug 1, 2015 at 3:27 PM, Tal Shorer <tal.shorer@...il.com> wrote:
>> Add a new options to trace Kconfig, CONFIG_TRACING_EVENTS_GPIO, that is
>> used for enabling/disabling compilation of gpio function trace events.
>>
>> Signed-off-by: Tal Shorer <tal.shorer@...il.com>
>> Acked-by: Linus Walleij <linus.walleij@...aro.org>
>> ---
>> include/trace/events/gpio.h | 4 ++++
>> kernel/trace/Kconfig | 7 +++++++
>> 2 files changed, 11 insertions(+)
>>
>> diff --git a/include/trace/events/gpio.h b/include/trace/events/gpio.h
>> index 927a8ad..2da73b9 100644
>> --- a/include/trace/events/gpio.h
>> +++ b/include/trace/events/gpio.h
>> @@ -1,6 +1,10 @@
>> #undef TRACE_SYSTEM
>> #define TRACE_SYSTEM gpio
>>
>> +#ifndef CONFIG_TRACING_EVENTS_GPIO
>> +#define NOTRACE
>> +#endif
>> +
>> #if !defined(_TRACE_GPIO_H) || defined(TRACE_HEADER_MULTI_READ)
>> #define _TRACE_GPIO_H
>>
>> diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
>> index 3b9a48a..67a1731 100644
>> --- a/kernel/trace/Kconfig
>> +++ b/kernel/trace/Kconfig
>> @@ -635,6 +635,13 @@ config TRACE_ENUM_MAP_FILE
>>
>> If unsure, say N
>>
>> +config TRACING_EVENTS_GPIO
>> + bool "Trace gpio events"
>> + depends on GPIOLIB
>> + default y
>> + help
>> + Enable tracing events for gpio subsystem
>> +
>> endif # FTRACE
>>
>> endif # TRACING_SUPPORT
>> --
>> 2.4.6
>>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists