>Not sure how fast Tom needs the common dma-iommu code for the x86 AMD iommu >conversion.
I am currently busy working on something else and won't be able to do/test the x86 AMD iommu conversion anytime soon. So I don't need the common dma-iommu code anytime soon. On 17 September 2018 at 14:33, Christoph Hellwig <h...@lst.de> wrote: > On Fri, Sep 14, 2018 at 01:48:59PM +0100, Will Deacon wrote: >> > As far as merging goes, I don't mind at all whether this goes via IOMMU, >> > or via dma-mapping provided Joerg's happy to ack it. >> >> I think it makes most sense for Joerg to take this series via his tree. > > FYI, I have WIP patches to move the arm dma-iommu wrappers to common > code: > > http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-maybe-coherent > > which will require some synchronization of the involved trees. In the > end it is iommu code, so the actual iommu patches should probably > go into the iommu tree after all, but it might have to pull in the > dma-mapping branch for that. Or we just punt it until the next merge > window. Not sure how fast Tom needs the common dma-iommu code for > the x86 AMD iommu conversion. _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
