From: Greg KH <gregkh@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: iio: add configuration option for debug support
Date: Mon, 5 Aug 2013 14:20:59 +0800 [thread overview]
Message-ID: <20130805062059.GA28434@kroah.com> (raw)
On Tue, Jul 16, 2013 at 01:56:00PM +0100, Otavio Salvador wrote:
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
> ---
> drivers/iio/Kconfig | 7 +++++++
> drivers/iio/Makefile | 2 ++
> 2 files changed, 9 insertions(+)
>
> diff --git a/drivers/iio/Kconfig b/drivers/iio/Kconfig
> index 524380c..b682f6f 100644
> --- a/drivers/iio/Kconfig
> +++ b/drivers/iio/Kconfig
> @@ -12,6 +12,13 @@ menuconfig IIO
>
> if IIO
>
> +config IIO_DEBUG
> + boolean "Debug support for Industrial I/O"
> + depends on DEBUG_KERNEL
> + help
> + Say "yes" to enable debug messaging (like dev_dbg and pr_debug)
> + support in Industrial I/O subsystem and drivers.
> +
> config IIO_BUFFER
> bool "Enable buffer support within IIO"
> help
> diff --git a/drivers/iio/Makefile b/drivers/iio/Makefile
> index 7a3866c..6e43e5b 100644
> --- a/drivers/iio/Makefile
> +++ b/drivers/iio/Makefile
> @@ -2,6 +2,8 @@
> # Makefile for the industrial I/O core.
> #
>
> +ccflags-$(CONFIG_IIO_DEBUG) := -DDEBUG
No, please don't do this. I'm going to revert this patch, as iio, and
the whole rest of the kernel, should be relying on the dynamic debug
code. Don't force a user to rebuild their kernel to enable/disable
debug stuff, that doesn't work well, if at all.
As it is, dev_dbg and pr_debug work just fine with dynamic debugging, no
need to explicitly make a new Kconfig option and set the DEBUG flag on
at all.
thanks,
greg k-h
next reply other threads:[~2013-08-05 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 6:20 Greg KH [this message]
2013-08-05 11:51 ` iio: add configuration option for debug support Otavio Salvador
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=20130805062059.GA28434@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.