public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [00/03] [RFC] USB debugging rework
Date: Fri, 8 Aug 2008 18:38:21 -0700	[thread overview]
Message-ID: <20080809013820.GA10910@kroah.com> (raw)

Hi all,

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.

(note, the recent rework of pr_debug() and dev_dbg() patches that have
been posted to lkml will probably obsolete these changes, but I don't
know when they will make it into mainline.  When they do, I'll be glad
to move these changes back to dev_dbg() to work with the rest of the
kernel.)

It seems that other parts of the kernel becides drivers/usb/core/ depend
on CONFIG_USB_DEBUG so I'll not submit these patches until I also fix up
them as well (drivers/net/usb is one big offender...)

Comments?

thanks,

greg k-h

             reply	other threads:[~2008-08-09  1:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-09  1:38 Greg KH [this message]
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 ` [00/03] [RFC] USB debugging rework Pete Zaitcev
2008-08-10  3:35   ` 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=20080809013820.GA10910@kroah.com \
    --to=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