From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 0/2] ohci-/ehci-platform: Change compatible string to generic-?hci
Date: Tue, 11 Feb 2014 09:53:15 -0800 [thread overview]
Message-ID: <7h7g917cz8.fsf@paris.lan> (raw)
In-Reply-To: <1392136529-5060-1-git-send-email-hdegoede@redhat.com> (Hans de Goede's message of "Tue, 11 Feb 2014 17:35:27 +0100")
Hans de Goede <hdegoede@redhat•com> writes:
> Hi Greg,
>
> And here is v2 of my ohci-/ehci-platform fixes for the regression of USB
> support on various ARM boards I caused in linux-next.
>
> As expected some people still did not like the ?hci-platform compatible
> string I went for in v1, hence this v2. The good news is it seems everyone
> seems to be able to live with generic-?hci as compatible now, so it seems this
> issue is finally settled.
>
> Please add these 2 patches to your usb-next tree, as said in the cover-letter
> of v1, I'm fine with you squashing these into the first 2 patches of my
> original series, but if you want them separate to preserve history that is
> fine too.
I tested this series on top of next-20140211 on the OMAP platforms where
I noticed the regressions, and confirm it fixes the problem.
Tested-by: Kevin Hilman <khilman@linaro•org>
Kevin
prev parent reply other threads:[~2014-02-11 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 16:35 [PATCH v2 0/2] ohci-/ehci-platform: Change compatible string to generic-?hci Hans de Goede
2014-02-11 16:35 ` [PATCH v2 1/2] ohci-platform: Change compatible string from usb-ohci to generic-ohci Hans de Goede
2014-02-11 16:43 ` Alan Stern
2014-02-12 8:45 ` Roger Quadros
2014-02-11 16:35 ` [PATCH v2 2/2] ehci-platform: Change compatible string from usb-ehci to generic-ehci Hans de Goede
2014-02-11 17:53 ` Kevin Hilman [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=7h7g917cz8.fsf@paris.lan \
--to=khilman@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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