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

> That's not quite true.  You could acquire dev->parent->sem always, just to
> be certain.  However USB shouldn't use this form of multithreaded probing
> in any case; it should instead use multiple threads for khubd.

Is anyone working on this (multiple threads for khubd)?

Ciao,

Duncan.
-
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/

---

• Follow-Ups:
  • Re: [Patch 3/3] Driver core: Per-subsystem multithreaded probing.
    • From: Alan Stern <[email protected]>

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

• Prev by Date: Re: Driver model.. expel legacy drivers?
• Next by Date: Re: Fwd: [PATCH] x86_64: typo in __assign_irq_vector when update pos for vector and offset
• Previous by thread: Re: [Patch 3/3] Driver core: Per-subsystem multithreaded probing.
• Next by thread: Re: [Patch 3/3] Driver core: Per-subsystem multithreaded probing.
• 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]