From: Stefan Wahren <wahrenst@gmx.net>
To: Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: iommu@lists.linux-foundation.org, linux-arm-kernel@lists.infradead.org
Subject: Build regression in Linux 5.3-rc5 with CONFIG_XEN=y
Date: Mon, 19 Aug 2019 20:37:00 +0200 [thread overview]
Message-ID: <ebd95b7c-d265-cbf1-be50-945db1dd06ad@gmx.net> (raw)
Hi,
i tried to cross compile arm/multi_v7_defconfig with CONFIG_XEN=y with
Linux 5.3-rc5 and i'm getting this:
arch/arm/mm/dma-mapping.c: In function ‘arch_setup_dma_ops’:
arch/arm/mm/dma-mapping.c:2347:5: error: ‘struct device’ has no member
named ‘dma_coherent’
dev->dma_coherent = coherent;
^~
arch/arm/mm/dma-mapping.c: At top level:
arch/arm/mm/dma-mapping.c:2385:6: error: redefinition of
‘arch_sync_dma_for_device’
void arch_sync_dma_for_device(struct device *dev, phys_addr_t paddr,
^~~~~~~~~~~~~~~~~~~~~~~~
In file included from arch/arm/mm/dma-mapping.c:18:0:
./include/linux/dma-noncoherent.h:67:20: note: previous definition of
‘arch_sync_dma_for_device’ was here
static inline void arch_sync_dma_for_device(struct device *dev,
^~~~~~~~~~~~~~~~~~~~~~~~
arch/arm/mm/dma-mapping.c:2392:6: error: redefinition of
‘arch_sync_dma_for_cpu’
void arch_sync_dma_for_cpu(struct device *dev, phys_addr_t paddr,
^~~~~~~~~~~~~~~~~~~~~
In file included from arch/arm/mm/dma-mapping.c:18:0:
./include/linux/dma-noncoherent.h:77:20: note: previous definition of
‘arch_sync_dma_for_cpu’ was here
static inline void arch_sync_dma_for_cpu(struct device *dev,
^~~~~~~~~~~~~~~~~~~~~
In file included from ./arch/arm/include/asm/page.h:149:0,
from ./arch/arm/include/asm/thread_info.h:14,
from ./include/linux/thread_info.h:38,
from ./include/asm-generic/preempt.h:5,
from ./arch/arm/include/generated/asm/preempt.h:1,
from ./include/linux/preempt.h:78,
from ./include/linux/spinlock.h:51,
from ./include/linux/seqlock.h:36,
from ./include/linux/time.h:6,
from ./include/linux/stat.h:19,
from ./include/linux/module.h:10,
from arch/arm/mm/dma-mapping.c:9:
There is no build issue with Linux 5.2, so this must be introduced with
5.3-rc. I hope you have a clue without bisecting this.
Regards
Stefan
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2019-08-19 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 18:37 Stefan Wahren [this message]
2019-08-19 19:02 ` Build regression in Linux 5.3-rc5 with CONFIG_XEN=y Robin Murphy
2019-08-19 19:12 ` Stefan Wahren
2019-08-20 1:24 ` Christoph Hellwig
2019-08-20 5:43 ` Stefan Wahren
2019-08-20 5:46 ` Christoph Hellwig
2019-08-21 5:55 ` Stefan Wahren
2019-08-21 5:56 ` Stefan Wahren
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=ebd95b7c-d265-cbf1-be50-945db1dd06ad@gmx.net \
--to=wahrenst@gmx.net \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).