From: Greg KH <greg@kroah.com>
To: "Munegowda, Keshava" <keshava_mgowda@ti.com>
Cc: "linux-usb-owner@vger.kernel.org"
<linux-usb-owner@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Gadiyar, Anand" <gadiyar@ti.com>,
"Kamat, Nishant" <nskamat@ti.com>
Subject: Re: [PATCH 0/5] usb: omap: prepare for OMAP4 EHCI and OHCI support
Date: Wed, 8 Sep 2010 01:55:45 -0700 [thread overview]
Message-ID: <20100908085545.GA15690@kroah.com> (raw)
In-Reply-To: <0680EC522D0CC943BC586913CF3768C003C2018B20@dbde02.ent.ti.com>
On Wed, Sep 08, 2010 at 01:21:04PM +0530, Munegowda, Keshava wrote:
> > -----Original Message-----
> > From: Munegowda, Keshava
> > Sent: Wednesday, August 18, 2010 8:26 AM
> > To: linux-usb@vger.kernel.org; linux-omap@vger.kernel.org
> > Cc: Munegowda, Keshava
> > Subject: [PATCH 0/5] usb: omap: prepare for OMAP4 EHCI and OHCI support
> >
> > This series does minor code cleanup in preparation of an upcoming
> > series to add support for EHCI and OHCI on the OMAP4 SoC.
> >
> > The changes are:
> > - Rename clock names to be consistent across OMAP3 and OMAP4
> > - Remove hardcoding of the number of TLL channels
> > - Move PHY reset earlier in the init sequence
> >
> > These patches do not make any changes to existing functionalities.
> >
> > Diffstat is below:
> >
> > drivers/usb/host/ehci-omap.c | 104 ++++++++++++-------------
> > drivers/usb/host/ohci-omap3.c | 55 ++++++-------
> > 2 files changed
> > ---
> > Keshava
>
> These are minor patches required for the adding omap4 support for
> EHCI and OHCI in near feature.
Do I already have them in my git tree? Did I forward them to Linus
already?
> Requesting for merge to the current merge window, so that the next
> set of EHCI and OHCI specific changes will be aligned with this patch set.
What do you mean by "current"? The merge window for .36 is closed now.
It's bugfixes-only at the moment. But I can easily queue up stuff for
.37 if you want to resend these.
thanks,
greg k-h
next prev parent reply other threads:[~2010-09-08 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 2:55 [PATCH 0/5] usb: omap: prepare for OMAP4 EHCI and OHCI support Keshava Munegowda
[not found] ` <1282100145-27485-1-git-send-email-keshava_mgowda-l0cyMroinI0@public.gmane.org>
2010-08-18 2:55 ` [PATCH 1/5] usb: ehci: omap: Update clock names to be same across OMAP3 and OMAP4 Keshava Munegowda
2010-08-18 2:55 ` [PATCH 2/5] usb: ehci: don't hard-code TLL channel count Keshava Munegowda
[not found] ` <1282100145-27485-3-git-send-email-keshava_mgowda-l0cyMroinI0@public.gmane.org>
2010-08-18 2:55 ` [PATCH 3/5] usb: ehci: relocate PHY reset code Keshava Munegowda
[not found] ` <1282100145-27485-4-git-send-email-keshava_mgowda-l0cyMroinI0@public.gmane.org>
2010-08-18 2:55 ` [PATCH 4/5] usb: ohci: omap: Update clock names to be same across OMAP3 and OMAP4 Keshava Munegowda
[not found] ` <1282100145-27485-5-git-send-email-keshava_mgowda-l0cyMroinI0@public.gmane.org>
2010-08-18 2:55 ` [PATCH 5/6] usb: ohci: don't hard-code TLL channel count Keshava Munegowda
[not found] ` <1282100145-27485-6-git-send-email-keshava_mgowda-l0cyMroinI0@public.gmane.org>
2010-08-18 15:37 ` Munegowda, Keshava
2010-08-19 6:03 ` Felipe Balbi
[not found] ` <20100819060308.GT4385-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2010-08-19 6:26 ` Munegowda, Keshava
2010-08-19 7:23 ` Felipe Balbi
2010-08-19 7:26 ` Munegowda, Keshava
2010-08-19 6:01 ` [PATCH 3/5] usb: ehci: relocate PHY reset code Felipe Balbi
[not found] ` <20100819060126.GS4385-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2010-08-20 9:41 ` Gadiyar, Anand
2010-09-08 7:51 ` [PATCH 0/5] usb: omap: prepare for OMAP4 EHCI and OHCI support Munegowda, Keshava
2010-09-08 8:55 ` Greg KH [this message]
2010-09-08 9:49 ` Munegowda, Keshava
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=20100908085545.GA15690@kroah.com \
--to=greg@kroah.com \
--cc=gadiyar@ti.com \
--cc=keshava_mgowda@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb-owner@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nskamat@ti.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