linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Ming Lei" <tom.leiming@gmail.com>,
	"Fengguang Wu" <fengguang.wu@intel.com>,
	"Bjørn Mork" <bjorn@mork.no>, "Oliver Neukum" <oneukum@suse.de>,
	"Sarah Sharp" <sarah.a.sharp@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"Lan, Tianyu" <tianyu.lan@intel.com>
Subject: Re: BUG: unable to handle kernel paging request in usb_match_id()
Date: Fri, 17 Aug 2012 07:42:53 -0700	[thread overview]
Message-ID: <20120817144253.GA12835@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1208171031100.25520-100000@netrider.rowland.org>

On Fri, Aug 17, 2012 at 10:38:16AM -0400, Alan Stern wrote:
> On Fri, 17 Aug 2012, Ming Lei wrote:
> 
> > But,  if HOTPLUG is not enabled, should device_add() trigger driver probe
> > further after kernel init is completed?  Or even devices should be allowed
> > to add into system?
> 
> Indeed, does it make any sense to have USB support at all if HOTPLUG
> isn't enabled?  Should USB select HOTPLUG?

Well, a long time ago people wanted to use USB but not have HOTPLUG
enabled in their systems for various (odd) embedded systems.  As it's
pretty hard to even turn off HOTPLUG these days, I'd be more likely to
just remove CONFIG_HOTPLUG entirely given the dynamic nature of almost
all systems.

So no, I don't think we should select HOTPLUG for USB.

greg k-h

  reply	other threads:[~2012-08-17 14:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-05  2:59 BUG: unable to handle kernel paging request in usb_match_id() Fengguang Wu
2012-08-05 16:58 ` Greg Kroah-Hartman
2012-08-17  2:00   ` Fengguang Wu
2012-08-17  3:48     ` Greg Kroah-Hartman
2012-08-17  5:44       ` Fengguang Wu
2012-08-17  8:52         ` Bjørn Mork
2012-08-17  9:07           ` Bjørn Mork
2012-08-17  9:27             ` Fengguang Wu
2012-08-17 10:24               ` Fengguang Wu
2012-08-17 12:16                 ` Ming Lei
2012-08-17 13:45                   ` Greg Kroah-Hartman
2012-08-17 14:38                   ` Alan Stern
2012-08-17 14:42                     ` Greg Kroah-Hartman [this message]
2012-08-18  0:58                       ` Ming Lei
2012-08-19 10:23                         ` Bjørn Mork
2012-08-19 14:35                           ` Greg Kroah-Hartman

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=20120817144253.GA12835@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bjorn@mork.no \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.de \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=stern@rowland.harvard.edu \
    --cc=tianyu.lan@intel.com \
    --cc=tom.leiming@gmail.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).