On 2020-09-24 10:25, Joerg Roedel wrote:
Hi Robin,
On Thu, Sep 24, 2020 at 10:08:46AM +0100, Robin Murphy wrote:
This should be fixed by https://lore.kernel.org/linux-iommu/daedc9364a19dc07487e4d07b8768b1e5934abd4.1600700881.git.robin.murphy@xxxxxxx/T/#u
(already in linux-next).
Thanks! The question remains why this goes through the dma-mapping tree,
was it caused by a patch there?
Yes, the issue was introduced by one of the changes in "dma-mapping:
introduce DMA range map, supplanting dma_pfn_offset", so it only existed
in the dma-mapping/for-next branch anyway.
Robin.
