>>And it's worth emphasizing that it doesn't affect the truth of
>>what I said: submitting after disconnect() is called is Wrong.
>>
>
>
> If this is the case, the first line of every disconnect for every driver
> should be:
> spin_lock_irqsave(desc->killlock, flags);
As Oliver mentioned, since this is called in a process context
it can just be spin_lock_irq().
It doesn't need to be a "kill lock". Your driver should already
have some lock guarding access to the fields of your driver's
driver state ... just use that.
- Dave
p.s. Re your question of how to call a function on module
unload, put it in whatever function you declare as
the module_exit function ...
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
