From: Tejas Joglekar <tejas.joglekar@synopsys.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Tejas Joglekar <tejas.joglekar@synopsys.com>,
Felipe Balbi <balbi@kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: John Youn <john.youn@synopsys.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"thinh.nguyen@synopsys.com" <thinh.nguyen@synopsys.com>
Subject: Re: [PATCH v2] usb: dwc3: gadget: Handle 0 xfer length for OUT EP
Date: Tue, 22 Jan 2019 04:28:10 +0000 [thread overview]
Message-ID: <6DE59E7D7B09224BB10C87AEADB5972692D6C5@IN01WEMBXB.internal.synopsys.com> (raw)
In-Reply-To: bb9c5c97-c2d7-5a96-a73b-abb4eef90916@cogentembedded.com
Hi,
On 1/21/2019 9:47 PM, Sergei Shtylyov wrote:
> Hello!
>
> On 01/21/2019 12:33 PM, Tejas Joglekar wrote:
>
>> For OUT endpoints, zero-length transfers require MaxPacketSize buffer as
>> per the DWC_usb3 programming guide 3.30a section 4.2.3.3.
>>
>> This patch fixes this by explicitly checking zero length
>> transfer to correctly pad up to MaxPacketSize.
>>
>> Fixes: c6267a51639b (usb: dwc3: gadget: align transfers to
>> wMaxPacketSize)
> Please enclose the summary in (""), no just (). And please never wrap it.
Sure, I will send v3.
>> Cc: stable@vger.kernel.org
>>
>> Signed-off-by: Tejas Joglekar <joglekar@synopsys.com>
> [...]
>
> MBR, Sergei
>
Thanks & Regards,
Tejas Joglekar
prev parent reply other threads:[~2019-01-22 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 9:33 [PATCH v2] usb: dwc3: gadget: Handle 0 xfer length for OUT EP Tejas Joglekar
2019-01-21 16:17 ` Sergei Shtylyov
2019-01-22 4:28 ` Tejas Joglekar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6DE59E7D7B09224BB10C87AEADB5972692D6C5@IN01WEMBXB.internal.synopsys.com \
--to=tejas.joglekar@synopsys.com \
--cc=balbi@kernel.org \
--cc=john.youn@synopsys.com \
--cc=linux-usb@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=stable@vger.kernel.org \
--cc=thinh.nguyen@synopsys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).