From: Steven Rostedt <rostedt@goodmis.org>
To: Tal Shorer <tal.shorer@gmail.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 2/2] tracing: gpio: add Kconfig option for enabling/disabling trace events
Date: Fri, 17 Jul 2015 14:36:06 -0400 [thread overview]
Message-ID: <20150717143606.200d97d7@gandalf.local.home> (raw)
In-Reply-To: <1437068376-24617-3-git-send-email-tal.shorer@gmail.com>
On Thu, 16 Jul 2015 20:39:36 +0300
Tal Shorer <tal.shorer@gmail.com> wrote:
> Add a new options to gpio Kconfig, CONFIG_GPIO_TRACING, that is used
> for enabling/disabling compilation of gpio function trace events.
>
If I can get acks from the gpio maintainers, I can take this in my
tree, as it depends on code that modifies the core tracing facility.
-- Steve
> Signed-off-by: Tal Shorer <tal.shorer@gmail.com>
> ---
> drivers/gpio/Kconfig | 7 +++++++
> include/trace/events/gpio.h | 4 ++++
> 2 files changed, 11 insertions(+)
>
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index c1e2ca3..2829e8e 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -88,6 +88,13 @@ config GPIO_SYSFS
> config GPIO_GENERIC
> tristate
>
> +config GPIO_TRACING
> + bool "gpio tracing"
> + depends on TRACING
> + help
> + Enable tracing for gpio subsystem
> +
> +
> # put drivers in the right section, in alphabetical order
>
> config GPIO_DA9052
> diff --git a/include/trace/events/gpio.h b/include/trace/events/gpio.h
> index 927a8ad..09af636 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_GPIO_TRACING
> +#define NOTRACE
> +#endif
> +
> #if !defined(_TRACE_GPIO_H) || defined(TRACE_HEADER_MULTI_READ)
> #define _TRACE_GPIO_H
>
next prev parent reply other threads:[~2015-07-17 18:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 20:21 [Patch RFC 0/2] tracing: allow disabling compilation of specific trace systems Tal Shorer
2015-06-20 20:21 ` [Patch RFC 1/2] " Tal Shorer
2015-07-13 18:34 ` Steven Rostedt
2015-07-13 21:38 ` Tal Shorer
2015-07-16 17:39 ` [PATCH v2 0/2] " Tal Shorer
2015-07-16 17:39 ` [PATCH v2 1/2] " Tal Shorer
2015-07-16 17:39 ` [PATCH v2 2/2] tracing: gpio: add Kconfig option for enabling/disabling trace events Tal Shorer
2015-07-17 18:36 ` Steven Rostedt [this message]
2015-07-18 10:12 ` Tal Shorer
2015-08-01 12:27 ` [Patch v3 0/2] tracing: allow disabling compilation of specific trace systems Tal Shorer
2015-08-01 12:27 ` [Patch v3 1/2] " Tal Shorer
2015-08-01 12:27 ` [Patch v3 2/2] tracing: gpio: add Kconfig option for enabling/disabling trace events Tal Shorer
2015-08-11 19:45 ` Tal Shorer
2015-09-23 14:54 ` Tal Shorer
2019-03-27 16:12 ` Uwe Kleine-König
2019-04-05 17:25 ` Linus Walleij
2015-07-27 11:57 ` [PATCH v2 " Linus Walleij
2015-06-20 20:21 ` [Patch RFC " Tal Shorer
2015-06-25 20:41 ` [Patch RFC 0/2] tracing: allow disabling compilation of specific trace systems Tal Shorer
2015-06-25 22:25 ` Steven Rostedt
2015-07-06 16:53 ` Tal Shorer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150717143606.200d97d7@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tal.shorer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).