From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: [BACKPORT PATCH 1/3] usb: dwc3: ep0: add dwc3_ep0_prepare_one_trb()
Date: Mon, 09 Jan 2017 13:22:42 +0200 [thread overview]
Message-ID: <87wpe4tr3x.fsf@linux.intel.com> (raw)
In-Reply-To: <20170109112356.GA19006@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Hi,
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> On Mon, Jan 09, 2017 at 01:03:31PM +0200, Felipe Balbi wrote:
>> commit 7931ec86c1b738e4e90e58c6d95e5f720d45ee56 upstream.
>>
>> For now this is just a cleanup patch, no functional
>> changes. We will be using the new function to fix a
>> bug introduced long ago by commit 0416e494ce7d
>> ("usb: dwc3: ep0: correct cache sync issue in case
>> of ep0_bounced") and further worsened by commit
>> c0bd5456a470 ("usb: dwc3: ep0: handle non maxpacket
>> aligned transfers > 512")
>>
>> Cc: <stable@vger.kernel.org>
>> Reported-by: Janusz Dziedzic <januszx.dziedzic@linux.intel.com>
>> Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
>> ---
>> drivers/usb/dwc3/ep0.c | 30 ++++++++++++++++++------------
>> 1 file changed, 18 insertions(+), 12 deletions(-)
>
> Thanks for these three patches, I got them to work on 4.4 as well :)
cool :-) I was about to backport them to v4.4. Glad I don't have to do
it :-)
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-01-09 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 11:03 [BACKPORT PATCH 1/3] usb: dwc3: ep0: add dwc3_ep0_prepare_one_trb() Felipe Balbi
2017-01-09 11:03 ` [BACKPORT PATCH 2/3] usb: dwc3: ep0: explicitly call dwc3_ep0_prepare_one_trb() Felipe Balbi
2017-01-09 11:03 ` [BACKPORT PATCH 3/3] usb: dwc3: gadget: always unmap EP0 requests Felipe Balbi
2017-01-09 11:23 ` [BACKPORT PATCH 1/3] usb: dwc3: ep0: add dwc3_ep0_prepare_one_trb() Greg Kroah-Hartman
2017-01-09 11:22 ` Felipe Balbi [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=87wpe4tr3x.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.