Re: [Patch 3/3] Driver core: Per-subsystem multithreaded probing.

On Mon, 16 Oct 2006, Cornelia Huck wrote:

> ->probe won't be called if the device is already being removed, but
> that still results in bus->remove being called without a prior ->probe
> (but not drv->probe since dev->driver is not set at that time).

One other thing I forgot to mention...  In device_attach(), if dev->driver 
is already set upon entry and the call to device_bind_driver() fails, 
dev->driver should be set to NULL before returning.  We don't want the 
device to appear to be bound when in fact it isn't.

Alan Stern

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [Patch 3/3] Driver core: Per-subsystem multithreaded probing.
    • From: Cornelia Huck <[email protected]>

• Prev by Date: [PATCH] esb2rom: use hotplug safe interfaces
• Next by Date: [PATCH] libata: Revamp blacklist support to allow multiple kinds of blacklisting flaws
• Previous by thread: Re: [Patch 3/3] Driver core: Per-subsystem multithreaded probing.
• Next by thread: [patch] slab: Fix a cpu hotplug race condition while tuning slab cpu caches
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]