> -----Original Message-----
> From: Greg KH [mailto:[email protected]]
> Sent: Wednesday, September 08, 2010 2:26 PM
> To: Munegowda, Keshava
> Cc: [email protected]; [email protected];
> [email protected]; Gadiyar,
> Anand; Kamat, Nishant
> Subject: Re: [PATCH 0/5] usb: omap: prepare for OMAP4 EHCI and OHCI support
>
> 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: [email protected]; [email protected]
> > > 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?
No. This series does not exist in your git tree.
>
> > 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.
Yes, Will retest these patches on 2.6.36.rc3 kernel and I will resend.
Thanks
Keshava Munegowda
>
> thanks,
>
> greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
