On Thu, Jun 07, 2012 at 03:49:35PM +0300, Artem Bityutskiy wrote: > On Thu, 2012-06-07 at 12:09 +0100, Russell King wrote: > > Add DMA engine support to the OMAP2 NAND driver. This supplements the > > private DMA API implementation contained within this driver, and the > > driver can be independently switched at build time between using DMA > > engine and the private DMA API. > > > > Tested-by: Grazvydas Ignotas <notasas@xxxxxxxxx> > > Signed-off-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx> > > I guess it is makes sense to make this stuff to go in via the OMAP tree. No, it makes sense to get this stuff via a single tree all together, because, as you can see from the thread structure, it isn't purely an OMAP thing. The OMAP stuff depends on a core set, as does a bunch of PL08x and SA11x0 changes. We can't stuff all that through the OMAP tree, that wouldn't make any sense. What probably should happen is that the tip of the OMAP stuff gets pulled by Tony into his tree, and we share those commits between my tree and his - and then it doesn't matter what goes in when and by whom. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
