diff options
| author | Dave Jiang <dave.jiang@intel.com> | 2015-08-20 08:44:09 -0700 |
|---|---|---|
| committer | Vinod Koul <vinod.koul@intel.com> | 2015-08-21 14:04:24 +0530 |
| commit | aaecdebc5855b77e2120d11c750630a3e60ffb10 (patch) | |
| tree | 9406965093d67aeca148f2e8a5d2d8731cf185fe /drivers/dma | |
| parent | 23a1ec304ae8fdd29235f864bd8193e9981c9bd1 (diff) | |
| download | linux-aaecdebc5855b77e2120d11c750630a3e60ffb10.tar.gz linux-aaecdebc5855b77e2120d11c750630a3e60ffb10.tar.bz2 linux-aaecdebc5855b77e2120d11c750630a3e60ffb10.zip | |
dmaengine: ioatdma: fix zero day warning on incompatible pointer type
The 32bit build is creating this warning. Since we don't expect anyone
actually use this on 32bit, restrict ioatdma to be built only on x86_64.
This issue has long existed and only reason it's surfacing due to code
refactoring.
drivers/dma/ioat/dma.c: In function 'ioat_timer_event':
>> drivers/dma/ioat/dma.c:870:39: warning: passing argument 2 of 'ioat_cleanup_preamble' from incompatible pointer type
if (ioat_cleanup_preamble(ioat_chan, &phys_complete))
^
drivers/dma/ioat/dma.c:577:13: note: expected 'u64 *' but argument is of type 'dma_addr_t *'
static bool ioat_cleanup_preamble(struct ioatdma_chan *ioat_chan,
^
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'drivers/dma')
| -rw-r--r-- | drivers/dma/Kconfig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig index 5244b44f5e67..0b114c8996af 100644 --- a/drivers/dma/Kconfig +++ b/drivers/dma/Kconfig @@ -74,7 +74,7 @@ config LPC18XX_DMAMUX config INTEL_IOATDMA tristate "Intel I/OAT DMA support" - depends on PCI && X86 + depends on PCI && X86_64 select DMA_ENGINE select DMA_ENGINE_RAID select DCA |