From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 2/2] ARM: at91/dt: update udc compatible strings
Date: Wed, 01 Jul 2015 13:35:10 -0700 [thread overview]
Message-ID: <7h8uazmxa9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <8ec182ab7c5186a64d605d0e174e750994586f02.1434530650.git.nicolas.ferre@atmel.com> (Nicolas Ferre's message of "Wed, 17 Jun 2015 10:59:05 +0200")
Nicolas Ferre <nicolas.ferre@atmel.com> writes:
> From: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> at91sam9g45, at91sam9x5 and sama5 SoCs should not use
> "atmel,at91sam9rl-udc" for their USB device compatible property since
> this compatible is attached to a specific hardware bug fix.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> Acked-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> Tested-by: Bo Shen <voice.shen@atmel.com>
> Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> Cc: <stable@vger.kernel.org> #4.0+
> ---
> Hi,
>
> This patch was forgotten while dealing with the series "usb: atmel_usba_udc:
> Rework errata handling". This patch and the previous one should be added to
> mainline as fixes, the soonest. In fact, the errata handling is now broken
> because of this desynchronization.
>
> We'll try to queue it during 4.2-rc phase for inclusion in arm-soc tree.
I've picked both of these up for the arm-soc/late branch which I'll try
to get in before -rc1, if not it will make it for -rc2.
Thanks,
Kevin
next prev parent reply other threads:[~2015-07-01 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 8:59 [RESEND PATCH 1/2] ARM: at91/dt: trivial: fix USB udc compatible string Nicolas Ferre
2015-06-17 8:59 ` [RESEND PATCH 2/2] ARM: at91/dt: update udc compatible strings Nicolas Ferre
2015-07-01 20:35 ` Kevin Hilman [this message]
2015-07-02 7:53 ` Nicolas Ferre
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=7h8uazmxa9.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).