* Jarkko Nikula <jhnik...@gmail.com> [090818 19:55]: > On Tue, 18 Aug 2009 14:45:41 +0100 > Mark Brown <broo...@opensource.wolfsonmicro.com> wrote: > > > On Tue, Aug 18, 2009 at 03:42:05PM +0200, Janusz Krzysztofik wrote: > > > > > And now, how is the patch 1/3 supposed to get into the mainline? Whom > > > should I ping from time to time to get it integrated? If not then, as > > > you know for sure, applying patch 2/3 whithout 1/3 will result in ASoC > > > support for OMAP1510 broken. > > > > Normally the OMAP tree, though that's possibly a bit tricky due to the > > ARM tree closing early. If Tony's OK with merging via the ALSA tree we > > could also apply the ARM patch there? > > I would say that it's better to keep in Tony's hand since otherwise > there can be risk for DMA code being out-of-sync as there are quite > frequent other PM, OMAP4, errata, etc. patches coming into it. > > Of course it means that OMAP1510 audio is broken until the patch 1/3 is > merged but probably patch can be merged as a fix if merge window is > missed.
Already replied in another part of the thread, but just for the archives: Since we don't have other dma or mcbsp patches going in right now, let's merge these all via the alsa list so audio keeps working. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
