From: Pete Zaitcev <zaitcev@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [00/03] [RFC] USB debugging rework
Date: Sat, 9 Aug 2008 16:04:22 -0600 [thread overview]
Message-ID: <20080809160422.48eae96b.zaitcev@redhat.com> (raw)
In-Reply-To: <20080809013820.GA10910@kroah.com>
On Fri, 8 Aug 2008 18:38:21 -0700, Greg KH <greg@kroah.com> wrote:
> I've been annoyed for a long time that we make users go off and rebuild
> their kernels just to enable usb debug messages. So finally, here's the
> start of fixing that issue.
In many cases usbmon does the job, and it's intended to be "always-on",
as to allow building it even on embedded kernels. Sure, it will not print
nice values of quirks and such, but that's a trade-off. I sort of hoped
that the switcheable explicit messages would generally die off. Look
at ub, it only has messages which indicate error conditions.
I'm not against your patch as such, it's a net improvement.
-- Pete
next prev parent reply other threads:[~2008-08-09 22:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 1:38 [00/03] [RFC] USB debugging rework Greg KH
2008-08-09 1:39 ` [01/03] USB: add CONFIG_USB_DEBUG_MESSAGES and usb_dbg() Greg KH
2008-08-09 1:39 ` [02/03] USB: convert the USB core code to use usb_dbg() Greg KH
2008-08-09 1:40 ` [03/03] USB: remove CONFIG_USB_DEBUG Greg KH
2008-08-09 15:04 ` [01/03] USB: add CONFIG_USB_DEBUG_MESSAGES and usb_dbg() Marcin Slusarz
2008-08-10 3:36 ` Greg KH
2008-08-09 22:04 ` Pete Zaitcev [this message]
2008-08-10 3:35 ` [00/03] [RFC] USB debugging rework Greg KH
2008-08-09 22:57 ` Frans Pop
2008-08-09 23:36 ` Felipe Balbi
2008-08-09 23:44 ` Felipe Balbi
2008-08-10 1:38 ` Greg KH
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=20080809160422.48eae96b.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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