From: Guenter Roeck <linux@roeck-us.net>
To: Chris Zankel <chris@zankel.net>, Max Filippov <jcmvbkbc@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-xtensa@linux-xtensa.org, linux-kernel@vger.kernel.org
Subject: xtensa build failures in -next due to DMA API changes
Date: Tue, 25 Aug 2015 13:07:56 -0700 [thread overview]
Message-ID: <20150825200756.GA25409@roeck-us.net> (raw)
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
next reply other threads:[~2015-08-25 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 20:07 Guenter Roeck [this message]
2015-08-25 20:15 ` xtensa build failures in -next due to DMA API changes Christoph Hellwig
2015-08-25 20:21 ` Guenter Roeck
2015-08-25 20:24 ` Christoph Hellwig
2015-08-26 7:53 ` Max Filippov
2015-08-26 7:59 ` Andrew Morton
2015-08-26 17:53 ` Chris Zankel
2015-08-26 17:41 ` Christoph Hellwig
2015-09-01 0:35 ` Chris Zankel
2015-08-25 20:22 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150825200756.GA25409@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=chris@zankel.net \
--cc=hch@lst.de \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.