From: Thierry Reding <thierry.reding@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: "J. German Rivera" <German.Rivera@freescale.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
kernel-build-reports@lists.linaro.org
Subject: Re: next-20160215 build: 3 failures 14 warnings (next-20160215)
Date: Mon, 15 Feb 2016 14:24:25 +0100 [thread overview]
Message-ID: <20160215132425.GA21048@ulmo> (raw)
In-Reply-To: <20160215121922.GH18988@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
On Mon, Feb 15, 2016 at 12:19:22PM +0000, Mark Brown wrote:
> On Mon, Feb 15, 2016 at 09:13:24AM +0000, Build bot for Mark Brown wrote:
>
> Today's linux-next fails to build an arm64 allmodconfig due to recent
> commits adding generic MSI and GICv3 support:
>
> > arm64-allmodconfig
> > ERROR: "msi_create_irq_domain" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
> > ERROR: "irq_chip_mask_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
> > ERROR: "free_msi_entry" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
> > ERROR: "msi_domain_alloc_irqs" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
> > ERROR: "of_msi_get_domain" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
> > ERROR: "irq_chip_eoi_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
> > ERROR: "msi_domain_set_affinity" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
> > ERROR: "msi_get_domain_info" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
> > ERROR: "msi_domain_free_irqs" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
> > ERROR: "alloc_msi_entry" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
> > ERROR: "irq_chip_unmask_parent" [drivers/staging/fsl-mc/bus/mc-bus-driver.ko] undefined!
>
> Presumably some missing select or dependency there...
I think this is caused by the MSI IRQ domain API not being exported.
I've just sent out a couple of patches that I've been carrying in my
local tree for a few days now.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-15 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 9:13 next-20160215 build: 3 failures 14 warnings (next-20160215) Build bot for Mark Brown
2016-02-15 12:19 ` Mark Brown
2016-02-15 13:24 ` Thierry Reding [this message]
2016-02-15 14:49 ` Mark Brown
2016-02-15 16:53 ` Thierry Reding
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=20160215132425.GA21048@ulmo \
--to=thierry.reding@gmail.com \
--cc=German.Rivera@freescale.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.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.