Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-17 Thread Alan Stern
On Mon, 16 Apr 2007, Greg KH wrote: > > > I've got a module which registers a struct device. (It represents a > > > virtual device, not a real one, but that doesn't matter.) > > Wait, that's the issue right there. > > Don't do that. > > devices should be created by busses or the platform core,

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-17 Thread Cornelia Huck
On Mon, 16 Apr 2007 15:12:47 -0700, Greg KH <[EMAIL PROTECTED]> wrote: > Ah, just found this original thread, now Cornelia's patches make more > sense... I would have included a pointer, but couldn't access marc yesterday evening, sorry... > > On Fri, Apr 13, 2007 at 11:24:58AM -0400, Alan Ster

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-16 Thread Greg KH
Ah, just found this original thread, now Cornelia's patches make more sense... On Fri, Apr 13, 2007 at 11:24:58AM -0400, Alan Stern wrote: > Tejun, it just occurred to me that you would be interested in this email > thread. Just to bring you up to speed, here's the original question: > > > I've

Re: [linux-usb-devel] How should an exit routine wait for release() callbacks?

2007-04-16 Thread Robert Marquardt
Alan Stern wrote: On the other hand, this proposal involves adding a fair amount of overhead (all those .owner fields) for a rather small benefit. And it involves modifying a core kernel subsystem (kernel/module.c). All to prevent certain unlikely sorts of errors when removing a module -- some