On Mon, Aug 17, 2015 at 10:06 AM, Christoph Hellwig wrote:
> Currently there are three valid implementations of dma_mapping_error:
>
> (1) call ->mapping_error
> (2) check for a hardcoded error code
> (3) always return 0
>
> This patch provides a common implementation that calls
On Mon, Aug 17, 2015 at 10:06 AM, Christoph Hellwig h...@lst.de wrote:
Currently there are three valid implementations of dma_mapping_error:
(1) call -mapping_error
(2) check for a hardcoded error code
(3) always return 0
This patch provides a common implementation that calls
Currently there are three valid implementations of dma_mapping_error:
(1) call ->mapping_error
(2) check for a hardcoded error code
(3) always return 0
This patch provides a common implementation that calls ->mapping_error
if present, then checks for DMA_ERROR_CODE if defined or otherwise
Currently there are three valid implementations of dma_mapping_error:
(1) call -mapping_error
(2) check for a hardcoded error code
(3) always return 0
This patch provides a common implementation that calls -mapping_error
if present, then checks for DMA_ERROR_CODE if defined or otherwise
Currently there are three valid implementations of dma_mapping_error:
(1) call ->mapping_error
(2) check for a hardcoded error code
(3) always return 0
This patch provides a common implementation that calls ->mapping_error
if present, then checks for DMA_ERROR_CODE if defined or otherwise
Currently there are three valid implementations of dma_mapping_error:
(1) call -mapping_error
(2) check for a hardcoded error code
(3) always return 0
This patch provides a common implementation that calls -mapping_error
if present, then checks for DMA_ERROR_CODE if defined or otherwise
6 matches
Mail list logo
