On Ponedjeljak 03 Prosinac 2001 00:43, you wrote:
> > From: Martin Diehl <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Date: Mon, 3 Dec 2001 00:21:14 +0100 (CET)
> > IMHO the returning of usb_submit_urb() should (and is, AFAICS) a clear
> > barrier indicating whether the completion handler wil
> > IMHO the returning of usb_submit_urb() should (and is, AFAICS) a clear
> > barrier indicating whether the completion handler will get called or not.
>
> Absolutely. Better say "The return code of usb_submit_urb()
> indicates if the callback was or will be called". If error
> is returned, no c
> From: Martin Diehl <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Mon, 3 Dec 2001 00:21:14 +0100 (CET)
> On Sun, 2 Dec 2001, Mark Burazin wrote:
>
> > usb_submit_urb() can fail, but it will call the completion handler, while
> > before it was not so, so I manually freed his urb and data
On Sun, 2 Dec 2001, Mark Burazin wrote:
> usb_submit_urb() can fail, but it will call the completion handler, while
> before it was not so, so I manually freed his urb and data when submit failed
Do I understand you correctly, you've seen situations where usb_submit_urb
returns some error (whi
Hi!
I was talking about some troubles with the switch to 2.4.16.
Found the bugger...
usb_submit_urb() can fail, but it will call the completion handler, while
before it was not so, so I manually freed his urb and data when submit failed
:-)
B...
--
Mark Burazin
[EMAIL PROTECTED]
---<
