[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190529230618.GC17556@Asurada-Nvidia.nvidia.com>
Date: Wed, 29 May 2019 16:06:19 -0700
From: Nicolin Chen <nicoleotsuka@...il.com>
To: Christoph Hellwig <hch@....de>
Cc: robin.murphy@....com, m.szyprowski@...sung.com, vdumpa@...dia.com,
linux@...linux.org.uk, catalin.marinas@....com,
will.deacon@....com, chris@...kel.net, jcmvbkbc@...il.com,
joro@...tes.org, dwmw2@...radead.org, tony@...mide.com,
akpm@...ux-foundation.org, sfr@...b.auug.org.au,
treding@...dia.com, keescook@...omium.org, iamjoonsoo.kim@....com,
wsa+renesas@...g-engineering.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-xtensa@...ux-xtensa.org, iommu@...ts.linux-foundation.org,
dann.frazier@...onical.com
Subject: Re: [PATCH v3 0/2] Optimize dma_*_from_contiguous calls
On Tue, May 28, 2019 at 08:04:24AM +0200, Christoph Hellwig wrote:
> Thanks,
>
> applied to dma-mapping for-next.
>
> Can you also send a conversion of drivers/iommu/dma-iommu.c to your
> new helpers against this tree?
>
> http://git.infradead.org/users/hch/dma-mapping.git/shortlog/refs/heads/for-next
I can. There is a reported regression with !CONFIG_DMA_CMA now
so I will do that after a fix is merged and the whole thing is
stable.
Thank you
Powered by blists - more mailing lists