Hi, Oliver,
Regarding skel_write, I see your current desgin only refuse its execution when> WRITES_IN_FLIGHT are on the fly, but this is not blocking IO due to write() will not wait before callback returns, right? Do you think it's unnecessary to support blocking IO on write or any special reason else?
----------------------------------------
> From: unicorn_wang@xxxxxxxxxxx
> To: oneukum@xxxxxxx
> CC: linux-usb@xxxxxxxxxxxxxxx
> Subject: RE: question on skel_read func of usb_skeleton.c
> Date: Thu, 11 Jul 2013 09:07:22 +0000
>
> Thank you, Oliver. I'm getting to understand your code :)
> ----------------------------------------
>> From: oneukum@xxxxxxx
>> To: unicorn_wang@xxxxxxxxxxx
>> CC: linux-usb@xxxxxxxxxxxxxxx
>> Subject: Re: question on skel_read func of usb_skeleton.c
>> Date: Tue, 9 Jul 2013 12:01:19 +0200
>>
>> On Tuesday 09 July 2013 09:32:35 WangChen wrote:
>>> Plus, regarding the reset case, urb-status will be non-zero, won't it?
>>
>> Only at the first call to read()
>>
>> Regards
>> Oliver
>> ےôè؛{.nا+‰·ں®‰†+%ٹثے±éف¶¥ٹwے؛{.nا+‰·¥ٹ{±ë)ي…وèw* jg¬±¨ ¶‰ڑژٹف¢jے¾«G«éے¢¸ ¢·¦j:+v‰¨ٹwèjطm¶ںےّ ¯ù ®w¥ٹàf£¢·hڑڈâْے†ظ¥
