From: Greg KH <greg@kroah.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] SuperH on-chip EHCI glue, v2
Date: Fri, 03 Dec 2010 20:13:50 +0000 [thread overview]
Message-ID: <20101203201350.GB17651@kroah.com> (raw)
In-Reply-To: <20101201091357.GA2982@linux-sh.org>
On Wed, Dec 01, 2010 at 06:13:57PM +0900, Paul Mundt wrote:
> This is a simple patch series for adding EHCI glue for the SuperH on-chip
> controller. It's largely modelled after the ohci-sh driver with clock
> management added on top, which I plan to move out to be shared between
> the two like Octeon presently does in a future patch -- this just hasn't
> been done yet since I need to go through and audit all of the SH OHCI
> users first.
>
> As before, if you don't have any issues with the series then you can feel
> free to pull the topic branch in to one of your trees as-is, or I can
> merge it via the SH tree (I don't have anything that depends on it, so
> I'm fine with whatever you prefer).
I've pulled this into my -next branch and pushed it out, so you don't
have to worry about it anymore.
thanks,
greg k-h
prev parent reply other threads:[~2010-12-03 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 9:13 [PATCH] SuperH on-chip EHCI glue, v2 Paul Mundt
2010-12-03 20:13 ` Greg KH [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=20101203201350.GB17651@kroah.com \
--to=greg@kroah.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