On Mon, 25 Jun 2007 01:16:24 -0700,
Greg KH <[EMAIL PROTECTED]> wrote:
[I'm a bit late to the party, but...]
> On Sun, Jun 24, 2007 at 11:04:13PM +0800, Huang, Ying wrote:
> > There does exist multithreaded device probing in current driver core
> > implementation, supposing two devices are
On Mon, 25 Jun 2007 01:16:24 -0700,
Greg KH [EMAIL PROTECTED] wrote:
[I'm a bit late to the party, but...]
On Sun, Jun 24, 2007 at 11:04:13PM +0800, Huang, Ying wrote:
There does exist multithreaded device probing in current driver core
implementation, supposing two devices are hot-plugged
On Sun, Jun 24, 2007 at 11:04:13PM +0800, Huang, Ying wrote:
> >From: Greg KH [mailto:[EMAIL PROTECTED]
> >I'm still not convinced that we need to add this kind of complexity to
> >the driver core, instead of just letting the individual driver
> >subsystems do this, if they want to do it.
>
> It
On Sun, Jun 24, 2007 at 11:04:13PM +0800, Huang, Ying wrote:
From: Greg KH [mailto:[EMAIL PROTECTED]
I'm still not convinced that we need to add this kind of complexity to
the driver core, instead of just letting the individual driver
subsystems do this, if they want to do it.
It may appear
>From: Greg KH [mailto:[EMAIL PROTECTED]
>I'm still not convinced that we need to add this kind of complexity to
>the driver core, instead of just letting the individual driver
>subsystems do this, if they want to do it.
It may appear not necessary that providing more multithreaded device
probing
From: Greg KH [mailto:[EMAIL PROTECTED]
I'm still not convinced that we need to add this kind of complexity to
the driver core, instead of just letting the individual driver
subsystems do this, if they want to do it.
It may appear not necessary that providing more multithreaded device
probing in
6 matches
Mail list logo
