From: Felipe Balbi <balbi@ti.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/4] usb: renesas_usbhs: fixes this driver in gadget mode (part2)
Date: Wed, 10 Sep 2014 13:49:10 +0000 [thread overview]
Message-ID: <20140910134910.GC667@saruman.home> (raw)
In-Reply-To: <53F725E3.4050304@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On Wed, Sep 10, 2014 at 07:33:27PM +0900, Yoshihiro Shimoda wrote:
> If we tested this driver as gadget, some issues below happened:
> - Oops happened if g_audio.
> - A usb enumeration may fail if we do insmod during connected the usb cable.
> - A transaction will not finish if g_zero.
> - A usb enumeration may fail after we re-connected the usb cable.
>
> This patch serias fixes them.
> This patch serias is based on Felipe's usb.git, testing/fixes branch.
> (commit id: 0b93a4c838fa10370d72f86fe712426ac63804de)
Can you start sending your patches as a thread ? It makes it easier to
find them. If you're already formatting patches to a directory, then all
you have to git send-email the difectory, instead of all files in that.
e.g.:
$ git format-patch -o patches --cover-letter -4
$ vim patches/0000-cover-letter*
$ git send-email --to balbi@ti.com --cc linux-usb@vger.kernel.org \
patches
With that said, do we need these patches in v3.17 final ? or only v3.18?
It's getting pretty late for v3.17-final...
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-10 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 11:13 [PATCH 0/4] usb: renesas_usbhs: fixes this driver in gadget mode Yoshihiro Shimoda
2014-09-10 10:33 ` [PATCH 0/4] usb: renesas_usbhs: fixes this driver in gadget mode (part2) Yoshihiro Shimoda
2014-09-10 13:49 ` Felipe Balbi [this message]
2014-09-11 0:11 ` Yoshihiro Shimoda
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=20140910134910.GC667@saruman.home \
--to=balbi@ti.com \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).