From: Jarod Wilson <jwilson@redhat.com>
To: linux1394-devel@lists.sourceforge.net
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: debug AT, AR, and selfID-complete events
Date: Mon, 10 Mar 2008 00:47:05 -0400 [thread overview]
Message-ID: <200803100047.05387.jwilson@redhat.com> (raw)
In-Reply-To: <tkrat.f96c4067f6a48f4a@s5r6.in-berlin.de>
On Sunday 09 March 2008 04:49:34 pm Stefan Richter wrote:
> This adds debug printks for asynchronous transmission and reception and
> for self ID reception. The debug code is per default deactivated by #if
> blocks.
>
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> ---
>
> I am undecided whether this is OK for mainline, and whether the debug
> options should become a Kconfig option or runtime options.
>
> It may be temporarily useful to the few driver developers. Do we want
> end users to provide us with debug logs of this kind? Then it should
> be one or two runtime options.
My vote would be to include this sort of thing with a run-time option to
enable the extra spew, since its a perfectly accepted standard for other
drivers. It ought to be extremely useful in determining whats going wrong
with end-user setups, particularly in cases where we can't reproduce the
problem (typically for lack of having the specific hardware in-house).
--
Jarod Wilson
jwilson@redhat.com
next prev parent reply other threads:[~2008-03-10 4:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 20:49 [PATCH] firewire: debug AT, AR, and selfID-complete events Stefan Richter
2008-03-10 4:47 ` Jarod Wilson [this message]
2008-03-10 22:28 ` [PATCH update] " Stefan Richter
2008-03-11 1:16 ` [PATCH] firewire: fw-ohci: untangle a mixed unsigned/signed expression Stefan Richter
2008-03-12 9:15 ` [PATCH update] firewire: debug AT, AR, and selfID-complete events Stefan Richter
2008-03-12 14:34 ` Jarod Wilson
2008-03-12 16:01 ` Stefan Richter
2008-03-15 1:57 ` Jarod Wilson
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=200803100047.05387.jwilson@redhat.com \
--to=jwilson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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