linux-kernel - xtensa build failures in -next due to DMA API changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150825200756.GA25409@roeck-us.net>
Date:	Tue, 25 Aug 2015 13:07:56 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Chris Zankel <chris@...kel.net>, Max Filippov <jcmvbkbc@...il.com>
Cc:	Christoph Hellwig <hch@....de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-xtensa@...ux-xtensa.org, linux-kernel@...r.kernel.org
Subject: xtensa build failures in -next due to DMA API changes

Hi,

xtensa builds fail in -next (again) as follows.

In file included from include/linux/dma-mapping.h:86:0,
                 from include/asm-generic/pci-dma-compat.h:7,
		 from ./arch/xtensa/include/asm/pci.h:59,
		from include/linux/pci.h:1492,
		from arch/xtensa/kernel/platform.c:16:
./arch/xtensa/include/asm/dma-mapping.h:40:21:
	error: redefinition of ‘dma_alloc_attrs’

In file included from ./arch/xtensa/include/asm/dma-mapping.h:33:0,
                 from include/linux/dma-mapping.h:86,
		 from include/asm-generic/pci-dma-compat.h:7,
		from ./arch/xtensa/include/asm/pci.h:59,
		from include/linux/pci.h:1492,
		from arch/xtensa/kernel/platform.c:16:
include/asm-generic/dma-mapping-common.h:245:21:
	note: previous definition of ‘dma_alloc_attrs’ was here

and many similar errors; it looks like all dma attribute functions have been
redefined.

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

Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/