On Tue, Jan 15, 2013 at 7:48 AM, Olof Johansson [off-list ref] wrote:
This series of patches only modify the ste_dma40 driver, there are no
corresponding changes under arch/arm that need to be coordinated or
considered w.r.t. merge conflicts. I.e. they all seem nicely isolated
to only the driver.
So is there a specific reason for why these shouldn't just go in
through the dmaengine tree?
One reason would be if there are DMA bindings to device tree coming
this merge window, as I'm told, and it implicates a lot of platform code
changes on top of this as we adopt to it.
But maybe this will be wholly confined to the DMAengine tree?
Yours,
Linus Walleij