On Wed, Jul 08, 2009 at 08:52:22AM -0700, Greg KH wrote: > On Wed, Jul 08, 2009 at 01:40:22PM +0200, Daniel Mack wrote: > > On Wed, Jul 08, 2009 at 12:12:31PM +0200, Sascha Hauer wrote: > > > On Thu, Jun 25, 2009 at 02:11:49PM +0200, Daniel Mack wrote: > > > > Here's a second round of EHCI patches for MX3 based systems. > > > > It contains corrections for all the comments of the previous series and > > > > was rebased to the current Linus master. > > > > > > > > I'd appreciate some tester's feedback :) > > > > > > > > Thanks, > > > > Daniel > > > > > > > > [PATCH 1/8] MX3: Add USB platform devices and resources > > > > [PATCH 2/8] ehci mxc: Fix clocks > > > > [PATCH 3/8] MX3: add additional USB pins to iomux > > > > [PATCH 4/8] USB: add slim framework for external transceivers > > > > [PATCH 5/8] USB: Add xcvr functions for NXP's ISP1504 transceiver > > > > [PATCH 6/8] MXC: Add support for ULPI Viewports > > > > [PATCH 7/8] Add EHCI support for MX27 and MX31 based boards > > > > [PATCH 8/8] MX3: add USB support for lilly1131 > > > > > > I'm fine with the latest versions of the patches. It'll need some fixup > > > for i.MX35, but I'll handle that later. > > > I wont mess with drivers/usb though without a clear ack from the USB > > > maintainer. So maybe it's best when you split up the series into a MXC > > > and a USB part and ask Greg to merge the USB part. You could encapsulate > > > the board support with #ifdef CONFIG_USB_ARCH_HAS_EHCI for the time > > > being to prevent merge dependencies. > > > > Well, the series is split already. Just leave out 4/8 and 5/8. And to > > not break the board support, leave out 8/8 as well - I will re-submit > > that as soon as the USB folks give their ACK on the rest. > > Did you cc: the proper maintainers for this ack? I didn't see it :) WOuld you tell me who those maintainers are? I Cc'ed the linux-usb list, believing that the right people read that list and chime in. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
