From: Felipe Balbi <balbi@ti.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: <balbi@ti.com>, <sylvain.rochet@finsecur.com>,
<r.baldyga@samsung.com>, <gregkh@linuxfoundation.org>,
<boris.brezillon@free-electrons.com>,
<alexandre.belloni@free-electrons.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: gadget: atmel_usba_udc: add ep capabilities support on device tree binding
Date: Fri, 18 Sep 2015 09:59:49 -0500 [thread overview]
Message-ID: <20150918145949.GC3126@saruman.tx.rr.com> (raw)
In-Reply-To: <1442588308-10201-1-git-send-email-nicolas.ferre@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Fri, Sep 18, 2015 at 04:58:28PM +0200, Nicolas Ferre wrote:
> From: Sylvain Rochet <sylvain.rochet@finsecur.com>
>
> The recently added endpoint capabilities flags verification breaks Atmel
> USBA because the endpoint configuration was only added when the driver
> is bound using the legacy pdata interface.
>
> Convert endpoint configuration to new capabilities model when driver is
> bound to a device tree as well.
>
> Signed-off-by: Sylvain Rochet <sylvain.rochet@finsecur.com>
> Fixes: 47bef3865115 ("usb: gadget: atmel_usba_udc: add ep capabilities support")
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> Felipe,
>
> As you've just requested, here is the same patch sent to linux-usb ml. I had
> added the "Fixes" and my SoB tags.
>
> For the record:
> It is considered as a fix for 4.3. Can you please queue it for the "4.3-rc"
> phase?
thanks, I'll take it for -rc3 (already sent my -rc2 pull request).
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-09-18 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 20:19 [PATCH linux-next] " Sylvain Rochet
2015-09-18 14:22 ` Nicolas Ferre
2015-09-18 14:27 ` Felipe Balbi
2015-09-18 14:58 ` [PATCH] " Nicolas Ferre
2015-09-18 14:59 ` 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=20150918145949.GC3126@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=r.baldyga@samsung.com \
--cc=sylvain.rochet@finsecur.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
Powered by JetHome