[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190415061824.GA18154@infradead.org>
Date: Sun, 14 Apr 2019 23:18:24 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Tom Murphy <tmurphy@...sta.com>
Cc: iommu@...ts.linux-foundation.org, Heiko Stuebner <heiko@...ech.de>,
Will Deacon <will.deacon@....com>,
David Brown <david.brown@...aro.org>,
linux-samsung-soc@...r.kernel.org, dima@...sta.com,
Krzysztof Kozlowski <krzk@...nel.org>,
linux-rockchip@...ts.infradead.org, Kukjin Kim <kgene@...nel.org>,
Andy Gross <andy.gross@...aro.org>,
Marc Zyngier <marc.zyngier@....com>,
linux-arm-msm@...r.kernel.org, linux-mediatek@...ts.infradead.org,
Matthias Brugger <matthias.bgg@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
murphyt7@....ie, Robin Murphy <robin.murphy@....com>
Subject: Re: [PATCH 0/9] iommu/amd: Convert the AMD iommu driver to the
dma-iommu api
Hi Tom,
can you rebase this on top of this series:
https://lists.linuxfoundation.org/pipermail/iommu/2019-March/034357.html
or the version addressing Robin's comments here:
http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-iommu-ops.3
so that we can avoid introducing more dma_map_ops boilerplate code?
Powered by blists - more mailing lists