From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 0/6] USB: EHCI multiplatform for 3.10
Date: Mon, 8 Apr 2013 09:42:09 -0700 [thread overview]
Message-ID: <20130408164209.GA13694@kroah.com> (raw)
In-Reply-To: <1364919844-1726-1-git-send-email-arnd@arndb.de>
On Tue, Apr 02, 2013 at 06:23:58PM +0200, Arnd Bergmann wrote:
> Hi Greg,
>
> Here are the EHCI patches that I think are good for inclusion in 3.10,
> I hope you are willing to include them after the debacle over these
> patches in 3.9.
>
> The patches are all logically independent but sorted by priority,
> so decide for yourself how many you want to take, starting at the
> first one. The first six patches all have an Ack from Alan Stern
> and from the respective ARM platform maintainers.
I don't see an ACK for the 6th patch from Alan, any reason for that?
I've applied the first 5 for now, if you want the 6th one applied,
please resend.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-usb@vger.kernel.org,
Manjunath Goudar <manjunath.goudar@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH V5 0/6] USB: EHCI multiplatform for 3.10
Date: Mon, 8 Apr 2013 09:42:09 -0700 [thread overview]
Message-ID: <20130408164209.GA13694@kroah.com> (raw)
In-Reply-To: <1364919844-1726-1-git-send-email-arnd@arndb.de>
On Tue, Apr 02, 2013 at 06:23:58PM +0200, Arnd Bergmann wrote:
> Hi Greg,
>
> Here are the EHCI patches that I think are good for inclusion in 3.10,
> I hope you are willing to include them after the debacle over these
> patches in 3.9.
>
> The patches are all logically independent but sorted by priority,
> so decide for yourself how many you want to take, starting at the
> first one. The first six patches all have an Ack from Alan Stern
> and from the respective ARM platform maintainers.
I don't see an ACK for the 6th patch from Alan, any reason for that?
I've applied the first 5 for now, if you want the 6th one applied,
please resend.
thanks,
greg k-h
next prev parent reply other threads:[~2013-04-08 16:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 16:23 [PATCH V5 0/6] USB: EHCI multiplatform for 3.10 Arnd Bergmann
2013-04-02 16:23 ` Arnd Bergmann
2013-04-02 16:23 ` [PATCH V5 1/6] USB: EHCI: make ehci-orion a separate driver Arnd Bergmann
2013-04-02 16:23 ` Arnd Bergmann
2013-04-02 16:24 ` [PATCH V5 2/6] USB: EHCI: make ehci-spear " Arnd Bergmann
2013-04-02 16:24 ` Arnd Bergmann
2013-04-02 16:24 ` [PATCH V5 3/6] USB: EHCI: make ehci-s5p " Arnd Bergmann
2013-04-02 16:24 ` Arnd Bergmann
2013-04-02 16:24 ` [PATCH V5 4/6] USB: EHCI: make ehci-atmel " Arnd Bergmann
2013-04-02 16:24 ` Arnd Bergmann
2013-04-02 16:24 ` [PATCH V5 5/6] USB: EHCI: make ehci-msm " Arnd Bergmann
2013-04-02 16:24 ` Arnd Bergmann
2013-04-02 16:24 ` [PATCH V5 6/6] USB: OHCI: avoid conflicting platform drivers Arnd Bergmann
2013-04-02 16:24 ` Arnd Bergmann
2013-04-17 20:57 ` Alan Stern
2013-04-17 20:57 ` Alan Stern
2013-04-08 16:42 ` Greg KH [this message]
2013-04-08 16:42 ` [PATCH V5 0/6] USB: EHCI multiplatform for 3.10 Greg KH
2013-04-08 16:48 ` Alan Stern
2013-04-08 16:48 ` Alan Stern
2013-04-08 17:14 ` Arnd Bergmann
2013-04-08 17:14 ` Arnd Bergmann
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=20130408164209.GA13694@kroah.com \
--to=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.