summaryrefslogtreecommitdiffstats
path: root/drivers/memstick
diff options
context:
space:
mode:
authorRussell King <rmk+kernel@arm.linux.org.uk>2013-06-10 17:56:16 +0200
committerRussell King <rmk+kernel@arm.linux.org.uk>2013-10-31 15:49:06 +0100
commit4cdbb4ff7fe456c43e9d6c6397e37380ff292520 (patch)
tree6d27e0e1ee944715fbc38d90c45a43c65799c8e5 /drivers/memstick
parentDMA-API: usb: use new dma_coerce_mask_and_coherent() (diff)
downloadlinux-4cdbb4ff7fe456c43e9d6c6397e37380ff292520.tar.xz
linux-4cdbb4ff7fe456c43e9d6c6397e37380ff292520.zip
DMA-API: staging: use dma_set_coherent_mask()
The correct way for a driver to specify the coherent DMA mask is not to directly access the field in the struct device, but to use dma_set_coherent_mask(). Only arch and bus code should access this member directly. Convert all direct write accesses to using the correct API. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'drivers/memstick')
0 files changed, 0 insertions, 0 deletions