From: Jeff Garzik <jgarzik@pobox.com>
To: Viresh Kumar <viresh.kumar@st.com>
Cc: linux-ide@vger.kernel.org, sshtylyov@mvista.com
Subject: Re: [PATCH Resend] ATA: Debugging options for the ATA subsystem
Date: Sat, 23 Jul 2011 18:17:29 -0400 [thread overview]
Message-ID: <4E2B4879.7000903@pobox.com> (raw)
In-Reply-To: <e6eda088c6d3761ac4f5d1719489be61356e3a8a.1307591731.git.viresh.kumar@st.com>
On 06/08/2011 11:56 PM, Viresh Kumar wrote:
> This adds Kconfig options for DEBUG and VERBOSE_DEBUG to the ATA subsystem
>
> Signed-off-by: Viresh Kumar<viresh.kumar@st.com>
> ---
> drivers/ata/Kconfig | 14 ++++++++++++++
> drivers/ata/Makefile | 2 ++
> 2 files changed, 16 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
> index 5dd1e4c..e1ac908 100644
> --- a/drivers/ata/Kconfig
> +++ b/drivers/ata/Kconfig
> @@ -22,6 +22,20 @@ menuconfig ATA
>
> if ATA
>
> +config ATA_DEBUG
> + bool "ATA debugging"
> + help
> + This is an option for use by developers; most people should
> + say N here. This enables ATA core and driver debugging.
> +
> +config ATA_VDEBUG
> + bool "ATA verbose debugging"
> + depends on ATA_DEBUG
> + help
> + This is an option for use by developers; most people should
> + say N here. This enables deeper (more verbose) debugging of
> + the ATA core and drivers.
> +
There does not seem to be a large, driving need for this. It is
straightforward to update the header file for the esoteric, voluminous
debugging.
If you are missing critical hardware or software errors, that is an
argument that those error messages should be outside of DEBUG/VDEBUG,
shipped with every kernel.
Jeff
next prev parent reply other threads:[~2011-07-23 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 3:56 [PATCH Resend] ATA: Debugging options for the ATA subsystem Viresh Kumar
2011-07-23 22:17 ` Jeff Garzik [this message]
2011-07-26 3:53 ` viresh kumar
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=4E2B4879.7000903@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@mvista.com \
--cc=viresh.kumar@st.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).