Per device coherent DMA map ops
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] Per device coherent DMA map ops
Quoted 9 lines · Rob Herring
Quoted 8 lines
I like those patches and I would like to take it to my dma-mapping-next tree, but I wonder how to handle merging of the last patch. Arnd, Olof - could You tell me how to do it? I assume that it should be somehow merged by arm-soc tree, so it depends on the earlier patches. Would it be enough if I take them to the topic branch? Then I can continue works on dma-mapping subsystem by merging that topic branch to my dma-mapping-next and you will also take it as a dependency for highbank patches. Am I right?
Quoted 5 lines
I'm fine with it all going in thru your tree. Seems a bit silly to deal with tracking the dependencies all for 1 patch. The only possible conflict I see is with the dts file and some other SATA related changes which will go in via the ata tree. But the merge is trivial and the conflict will be there either with your tree or arm-soc.
Right. I see no problem having this patch go through the dma-mapping tree.
Arnd