> - it's called after usblp_write() did an illegal (racey) thing, looking
> at urb->status outside the completion function. (does anyone know
> why usblp_write() isn't just issuing a single write for that buffer?)
It's safe because we previously check for wcomplete==1.
The completion handler has run.
But I can't for the life of me tell what, except for unplugging,
terminates the while loop if there's an actual error as a result
of the URB.
Regards
Oliver
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
