From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>
Cc: "J. German Rivera" <German.Rivera@freescale•com>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
Thierry Reding <thierry.reding@gmail•com>,
kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org
Subject: Re: next-20160217 build: 3 failures 14 warnings (next-20160217)
Date: Thu, 18 Feb 2016 11:31:42 +1100 [thread overview]
Message-ID: <20160218113142.452fd8a0@canb.auug.org.au> (raw)
In-Reply-To: <20160217112225.GM7544@sirena.org.uk>
Hi Mark,
On Wed, 17 Feb 2016 11:22:25 +0000 Mark Brown <broonie@kernel•org> wrote:
>
> On Wed, Feb 17, 2016 at 08:28:37AM +0000, Build bot for Mark Brown wrote:
>
> > 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!
>
> The fsl-mc code is still breaking the build in -next, can we please drop
> the code or mark the driver as built in only until the MSI symbol
> exports are available? This is making it difficult to spot other
> errors.
I will add a merge fixup patch for the staging tree that makes
CONFIG_FSL_MC_BUS depend on CONFIG_BROKEN. Sorry, I should have done
this when it first came to light.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-02-18 0:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 8:28 next-20160217 build: 3 failures 14 warnings (next-20160217) Build bot for Mark Brown
2016-02-17 11:22 ` Mark Brown
2016-02-18 0:31 ` Stephen Rothwell [this message]
2016-02-18 13:43 ` Mark Brown
2016-02-18 13:59 ` Thierry Reding
2016-02-19 22:48 ` Greg Kroah-Hartman
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=20160218113142.452fd8a0@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=German.Rivera@freescale$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=thierry.reding@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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