For many years we've had the dma_alloc_attrs API that is more flexible
than dma_alloc_noncoherent. This series moves the remaining users over
to the attrs API.
After half of the series went in for the last merge window I'd really
like to merge the remainer. Any chance to get some ACKs/reviews fo
No users left, everyone switched to the _attrs versions.
Signed-off-by: Christoph Hellwig
---
Documentation/DMA-API.txt| 30 --
arch/metag/include/asm/dma-mapping.h | 2 +-
arch/nios2/include/asm/dma-mapping.h | 2 +-
arch/tile/include/asm/dma-mapping.h
From: Christoph Hellwig
> Sent: 16 June 2017 08:17
>
> For many years we've had the dma_alloc_attrs API that is more flexible
> than dma_alloc_noncoherent. This series moves the remaining users over
> to the attrs API.
And most of the callers probably only want to specify 'noncoherent'.
Grepping
No users left, everyone switched to the _attrs versions.
Signed-off-by: Christoph Hellwig
---
Documentation/DMA-API.txt| 30 --
arch/metag/include/asm/dma-mapping.h | 2 +-
arch/nios2/include/asm/dma-mapping.h | 2 +-
arch/tile/include/asm/dma-mapping.h
For many years we've had the dma_alloc_attrs API that is more flexible
than dma_alloc_noncoherent. This series moves the remaining users over
to the attrs API.