Re: xtensa build failures in -next due to DMA API changes

[Christoph Hellwig]

Hi Guenter,

> The problem seems to have been introduced with changes made by Christoph
> Hellwig, coming in through Andrew's tree. Copying them here for comments.

xtensa doesn't use the generic dma map implementation, so it shouldn't
include dma-mapping-common.h anywhere, and in my tree it doesn't.

Can you do a git-grep for dma-mapping-common.h on the tree that you
see this error on?  Nothing but arch/*/include/asm/dma-mapping.h should
include it.  In my tree it's all fine:

Documentation/DMA-API-HOWTO.txt:   can use include/linux/asm-generic/dma-mapping-common.h. It's a
arch/alpha/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/arm/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/arm64/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/h8300/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/hexagon/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/ia64/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/microblaze/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/mips/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/openrisc/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/powerpc/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/s390/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/sh/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/sparc/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/tile/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/unicore32/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
arch/x86/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/