On Thu, 15 Jun 2006, Greg KH wrote: > > It's bloody difficult to do any serious searches through the mailing list > > archives. If you know of a good way to do it, I'd like to hear what it > > is. > > Subscribe a gmail account to the mailing list, add a tag for it, and > then use gmail to search. > > Or just subscribe to the list, and archive everything and use good > search tools to find things (mairix works very well). > > I do both and it seems to handle all of the different situations (the > gmail one is fun to play with, but a pain to get patches out of).
Hm. Not much help when searching for messages from before the subscription began. It would be nice if there was a central repository with good search tools that everyone could use. But I'm not volunteering to set one up! > > In this case, you probably mean something like this: > > > > --- usb-2.6.orig/include/linux/device.h > > +++ usb-2.6/include/linux/device.h > > @@ -404,7 +404,8 @@ extern void firmware_unregister(struct s > > > > /* debugging and troubleshooting/diagnostic helpers. */ > > #define dev_printk(level, dev, format, arg...) \ > > - printk(level "%s %s: " format , (dev)->driver ? (dev)->driver->name : > > "" , (dev)->bus_id , ## arg) > > + printk(level "%s %s: " format , (dev)->driver ? (dev)->driver->name : \ > > + (dev)->bus->name , (dev)->bus_id , ## arg) > > > > #ifdef DEBUG > > #define dev_dbg(dev, format, arg...) \ > > > > > > Is this right? It definitely will solve the problem I was referring to. > > Yes, that's it. I'll go add that to my trees, thanks. > > Hm, need to check that the device is attached to a bus, because that's > not always true... You're right. This is beginning to look a little complicated for inline code. Some sort of va_printf approach might be more efficient. Alan Stern _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
