From: Felipe Balbi <balbi@ti.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>
Subject: [GIT PULL] USB fixes for v3.18-rc5
Date: Mon, 10 Nov 2014 14:52:59 -0600 [thread overview]
Message-ID: <1415652779-31904-1-git-send-email-balbi@ti.com> (raw)
Hi Greg,
Here's another minor for v3.18-rc5. Please consider
merging to your usb-linus branch.
Tested with AM437x SK and testusb.
cheers
The following changes since commit 206c5f60a3d902bc4b56dab2de3e88de5eb06108:
Linux 3.18-rc4 (2014-11-09 14:55:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git tags/fixes-for-v3.18-rc5
for you to fetch changes up to 520fe7633692181bb6d1560d655fbdfbb7c05aaa:
usb: dwc3: ep0: fix for dead code (2014-11-10 14:39:44 -0600)
----------------------------------------------------------------
usb: fixes for v3.18-rc5
Just one fix here on dwc3 which fixes a minor
bug caused by a fix that went in this v3.18-rc
cycle.
The corner case is minimal as it can only be
reproduced with back-to-back Setup transfers
(without starting data or status phase) by
means of a LeCroy USB Trainer, where we can
generate USB packets any way we like.
Signed-off-by: Felipe Balbi <balbi@ti.com>
----------------------------------------------------------------
Felipe Balbi (1):
usb: dwc3: ep0: fix for dead code
drivers/usb/dwc3/ep0.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2014-11-10 20:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 20:52 Felipe Balbi [this message]
2014-11-13 18:05 ` Felipe Balbi
2014-11-13 19:11 ` Greg KH
2014-11-13 19:13 ` Felipe Balbi
2014-11-13 19:18 ` Greg KH
2014-11-13 20:05 ` Felipe Balbi
2014-11-13 19:14 ` Greg KH
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=1415652779-31904-1-git-send-email-balbi@ti.com \
--to=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®