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 17:53:54 +0100 [thread overview]
Message-ID: <20160215165354.GA25830@ulmo> (raw)
In-Reply-To: <20160215144901.GL18988@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]
On Mon, Feb 15, 2016 at 02:49:01PM +0000, Mark Brown wrote:
> On Mon, Feb 15, 2016 at 02:24:25PM +0100, Thierry Reding wrote:
> > On Mon, Feb 15, 2016 at 12:19:22PM +0000, Mark Brown wrote:
>
> > > 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.
>
> Yeah, that'd do it.
I just noticed that the build still fails after fixing those up:
./drivers/firmware/efi/libstub/lib.a(lib-fdt_ro.stub.o): In function `__efistub_fdt_stringlist_count':
__efistub_fdt_ro.c:(.init.text+0xe48): undefined reference to `__efistub_strnlen'
__efistub_fdt_ro.c:(.init.text+0xe48): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `__efistub_strnlen'
./drivers/firmware/efi/libstub/lib.a(lib-fdt_ro.stub.o): In function `__efistub_fdt_stringlist_search':
__efistub_fdt_ro.c:(.init.text+0xf18): undefined reference to `__efistub_strnlen'
__efistub_fdt_ro.c:(.init.text+0xf18): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `__efistub_strnlen'
./drivers/firmware/efi/libstub/lib.a(lib-fdt_ro.stub.o): In function `__efistub_fdt_stringlist_get':
__efistub_fdt_ro.c:(.init.text+0x1014): undefined reference to `__efistub_strnlen'
__efistub_fdt_ro.c:(.init.text+0x1014): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `__efistub_strnlen'
That happens on the ARM64 defconfig as well, but I have no idea what's
going on here.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-02-15 16:53 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
2016-02-15 14:49 ` Mark Brown
2016-02-15 16:53 ` Thierry Reding [this message]
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=20160215165354.GA25830@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 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).