On Friday 26 December 2008, Alan Stern wrote: > Usually separating out patches by subsystem results in independent > sub-series that can build just fine. But sometimes, like now, it > doesn't. This seems to be unavoidable. It gets even worse when there > are inter-related patches affecting multiple subsystems that don't all > have the same maintainer! Yes. This case involves only two ... three subsystems isn't all that uncommon, four verges on un-workable. > > Do you just want to provide an update to that patch of > > yours (usb-enhance-usage-of-pm_message_t.patch) which > > seems to be the proximate cause of the build bugs? > > We can handle this any way Greg deems best. Since the fix-misspellings > patch is already in his tree, the easiest approach is to do nothing and > wait for it to be sent in along with everything else during the > upcoming merge window. Did you verify that the fix-misspellings patch suffices for the OTG code paths? Not unrelated: 2.6.29-rc1 should be able to run most of the goodies on those Gumstix.com Overo boards, excepting maybe the framebuffer (DVI, S-Video), in mainline. (The MMC and USB-OTG transceiver drivers will merge, giving easy access to a rootfs and networking.) That's first widely available USB OTG platform for Linux, along with www.beagleboard.org of course. So it'll be easier to catch such stuff. - Dave -- 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
