Re: some question about usb_interrupt_msg

[vichy]

hi Alan:

2014-05-22 22:14 GMT+08:00 Alan Stern :
> On Thu, 22 May 2014, vichy wrote:
>
>> hi all:
>> I see usb_interrupt_msg do nothing but call usb_bulk_msg.
>> Why we still keep usb_interrupt_msg?
>> for old api compatibility?
>
> That's right.  Also because it gives an indication to the reader about
> what type of transfer is being performed.
I got it.
appreciate your kind reply ^^
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: some question about usb_interrupt_msg

[Alan Stern]

On Thu, 22 May 2014, vichy wrote:

> hi all:
> I see usb_interrupt_msg do nothing but call usb_bulk_msg.
> Why we still keep usb_interrupt_msg?
> for old api compatibility?

That's right.  Also because it gives an indication to the reader about 
what type of transfer is being performed.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

some question about usb_interrupt_msg

[vichy]

hi all:
I see usb_interrupt_msg do nothing but call usb_bulk_msg.
Why we still keep usb_interrupt_msg?
for old api compatibility?

thanks for your help in advance,
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html