![]() | |||||||||||||
Messages in this thread |
On Tue, Jul 25, 2006 at 11:15:53PM +0100, James Courtier-Dutton wrote: > Greg KH wrote: > > During the kernel summit, I was reminded by the wish by some people to > > do device probing in parallel, so I created the following patch. It > > offers up the ability for the driver core to create a new thread for > > every driver<->device probe call. To enable this, the driver needs to > > have the multithread_probe flag set to 1, otherwise the "traditional" > > sequencial probe happens. > > What happens about the logging? Nothing, it works just fine. A little messy perhaps, but it's all there. I don't see the problem here... > Surely one would want the output from one probe to be output into the > log as a block, and not mix the output from multiple simultaneous probes. Why not? Each subsystem already uses the dev_printk() for the most part for their logging messages, so it's easy to figure out what is going on. thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-07-26 09:31 [from the cache] ©2003-2008 | |||||||||||||