From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20160225 build: 2 failures 44 warnings (next-20160225)
Date: Fri, 26 Feb 2016 09:08:30 +0100 [thread overview]
Message-ID: <20160226090830.41a63a86@free-electrons.com> (raw)
In-Reply-To: <20160226030411.GK18327@sirena.org.uk>
Mark,
On Fri, 26 Feb 2016 12:04:11 +0900, Mark Brown wrote:
> Today's -next fails to build an arm64 allmodconfig due to:
>
> > arm64-allmodconfig
> > ../drivers/pci/host/pci-mvebu.c:755:12: error: dereferencing pointer to incomplete type 'struct pci_sys_data'
> > ../drivers/pci/host/pci-mvebu.c:855:31: error: dereferencing pointer to incomplete type 'struct pci_sys_data'
> > ../drivers/pci/host/pci-mvebu.c:904:16: error: storage size of 'hw' isn't known
> > ../drivers/pci/host/pci-mvebu.c:919:2: error: implicit declaration of function 'pci_common_init_dev' [-Werror=implicit-function-declaration]
> > ../drivers/pci/host/pci-mvebu.c:1282:3: error: implicit declaration of function 'pci_ioremap_io' [-Werror=implicit-function-declaration]
>
> caused by b4f596b19624 (arm64: add mvebu architecture entry) which
> enables MVBEU on arm64, the commit was present for a little while and
> the error cropped up but didn't get reported due to other things masking
> it. This looks like the driver needs modernization and probably ought
> to have a !ARM64 dependency for now.
This has already been fixed by:
[PATCH] PCI: mvebu: Restrict build to 32-bit ARM
submitted by Thierry Redding. I'm Cc'ing Bjorn, who is the one in
charge of merging this fix.
Thanks for reporting!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-26 8:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1aYsmb-0006qb-76@optimist>
2016-02-26 3:04 ` next-20160225 build: 2 failures 44 warnings (next-20160225) Mark Brown
2016-02-26 8:08 ` Thomas Petazzoni [this message]
2016-02-26 19:34 ` Bjorn Helgaas
2016-02-26 3:09 ` Mark Brown
2016-02-26 7:41 ` Guenter Roeck
2016-02-26 8:21 ` Thomas Petazzoni
2016-02-26 8:14 ` Thomas Petazzoni
2016-02-26 12:12 ` Mark Brown
2016-02-27 14:40 ` Thomas Petazzoni
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=20160226090830.41a63a86@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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 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).