There is no need to call read_fifo for zero byte length.
Signed-off-by: Ajay Kumar Gupta
---
drivers/usb/musb/musb_gadget_ep0.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/musb/musb_gadget_ep0.c
b/drivers/usb/musb/musb_gadget_ep0.c
index e40d764..d7
Hello.
On 19-07-2012 11:55, Ajay Kumar Gupta wrote:
There is no need to call read_fifo for zero byte length.
The same as there's no need to write, and not only here?
Signed-off-by: Ajay Kumar Gupta
---
drivers/usb/musb/musb_gadget_ep0.c |6 --
1 files changed, 4 insertions(+)
Hi,
> On 19-07-2012 11:55, Ajay Kumar Gupta wrote:
>
> > There is no need to call read_fifo for zero byte length.
>
> The same as there's no need to write, and not only here?
Yes, it applies to write also but seems write is taken care
for zero byte length.
>
> > Signed-off-by: Ajay Kumar
On 07/19/2012 03:22 PM, Gupta, Ajay Kumar wrote:
>>> There is no need to call read_fifo for zero byte length.
>> The same as there's no need to write, and not only here?
> Yes, it applies to write also but seems write is taken care
> for zero byte length.
Frankly speaking, I don't see i
Hi,
> On 07/19/2012 03:22 PM, Gupta, Ajay Kumar wrote:
>
> >>> There is no need to call read_fifo for zero byte length.
>
> >> The same as there's no need to write, and not only here?
>
> > Yes, it applies to write also but seems write is taken care
> > for zero byte length.
>
>Frankly
