* [Patch 0/3] Driver core: Some probing changes
@ 2006-10-16 8:44 Cornelia Huck
2006-10-16 14:39 ` Alan Stern
0 siblings, 1 reply; 3+ messages in thread
From: Cornelia Huck @ 2006-10-16 8:44 UTC (permalink / raw)
To: Greg K-H; +Cc: Alan Stern, linux-kernel
Hi,
the following patches attempt to fix some issues in the current device
probing code:
[1/3] Don't stop probing on ->probe errors.
[2/3] Change function call order in device_bind_driver().
[3/3] Per-subsystem multithreaded probing.
Patches are against -gkh tree. Works for me on s390 and on i386 with
pci multithreaded probing enabled. (I also enabled multithreaded
probing on the css and ccw busses in order to test the code on s390,
but this doesn't make much sense since we already do async device
recognition, so I'm not sending a patch.)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Patch 0/3] Driver core: Some probing changes
2006-10-16 8:44 [Patch 0/3] Driver core: Some probing changes Cornelia Huck
@ 2006-10-16 14:39 ` Alan Stern
2006-10-16 14:59 ` Cornelia Huck
0 siblings, 1 reply; 3+ messages in thread
From: Alan Stern @ 2006-10-16 14:39 UTC (permalink / raw)
To: Cornelia Huck; +Cc: Greg K-H, linux-kernel
On Mon, 16 Oct 2006, Cornelia Huck wrote:
> Hi,
>
> the following patches attempt to fix some issues in the current device
> probing code:
>
> [1/3] Don't stop probing on ->probe errors.
> [2/3] Change function call order in device_bind_driver().
> [3/3] Per-subsystem multithreaded probing.
>
> Patches are against -gkh tree. Works for me on s390 and on i386 with
> pci multithreaded probing enabled. (I also enabled multithreaded
> probing on the css and ccw busses in order to test the code on s390,
> but this doesn't make much sense since we already do async device
> recognition, so I'm not sending a patch.)
Your patch 2 looks fine.
Patch 1 is somewhat questionable. Certainly the log message reporting the
error should be left in. The other issue is whether to continue with
probing other drivers. I guess there's no reason not to; stopping short
was merely an optimization.
I'll discuss patch 3 in a separate message.
Alan Stern
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Patch 0/3] Driver core: Some probing changes
2006-10-16 14:39 ` Alan Stern
@ 2006-10-16 14:59 ` Cornelia Huck
0 siblings, 0 replies; 3+ messages in thread
From: Cornelia Huck @ 2006-10-16 14:59 UTC (permalink / raw)
To: Alan Stern; +Cc: Greg K-H, linux-kernel
On Mon, 16 Oct 2006 10:39:28 -0400 (EDT),
Alan Stern <stern@rowland.harvard.edu> wrote:
> Patch 1 is somewhat questionable. Certainly the log message reporting the
> error should be left in.
OK, that makes sense. I'll do an updated patch.
> The other issue is whether to continue with
> probing other drivers. I guess there's no reason not to; stopping short
> was merely an optimization.
And not stopping also solves the "broken driver prevents any other
driver from matching" problem.
--
Cornelia Huck
Linux for zSeries Developer
Tel.: +49-7031-16-4837, Mail: cornelia.huck@de.ibm.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-10-16 14:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-10-16 8:44 [Patch 0/3] Driver core: Some probing changes Cornelia Huck
2006-10-16 14:39 ` Alan Stern
2006-10-16 14:59 ` Cornelia Huck
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®