From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: next build: 143 builds: 2 failed, 141 passed, 2 errors, 2 warnings (next-20160909)
Date: Fri, 09 Sep 2016 13:18:31 +0200 [thread overview]
Message-ID: <2582793.W17ckCts1B@wuerfel> (raw)
In-Reply-To: <57d26402.eeb8c20a.ba0e2.8bbb@mx.google.com>
On Friday, September 9, 2016 12:25:54 AM CEST kernelci. org bot wrote:
> next build: 143 builds: 2 failed, 141 passed, 2 errors, 2 warnings (next-20160909)
This is pretty good, here is what's left:
> rpc_defconfig (arm) ? FAIL, 1 error, 0 warnings, 0 section mismatches
>
> Errors:
> fs/fat/dir.c:758:424: internal compiler error: Segmentation fault
Could we please update the gcc build on kernelci.org from "Linaro GCC 5.3-2016.02"
to the following version (Linaro GCC 5.3-2016.05) or later?
> allmodconfig (arm64) ? FAIL, 1 error, 0 warnings, 0 section mismatches
>
> Errors:
> ERROR: "memblock_is_memory" [drivers/hwmon/xgene-hwmon.ko] undefined!
Currently under discussion, no patch yet.
> Warnings summary:
>
> 2 lib/raid6/recov_avx512.c:387:2: warning: #warning "your version of binutils lacks AVX512 support" [-Wcpp]
This is for the x86 native binutils, which may be a bit trickier to
update. Apparently the minimum assembler version required for this is
from binutils-2.25, released Jan 13, 2015.
Arnd
next parent reply other threads:[~2016-09-09 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57d26402.eeb8c20a.ba0e2.8bbb@mx.google.com>
2016-09-09 11:18 ` Arnd Bergmann [this message]
2016-09-09 17:00 ` next build: 143 builds: 2 failed, 141 passed, 2 errors, 2 warnings (next-20160909) Kevin Hilman
2016-09-09 17:19 ` Mark Brown
2016-09-09 19:25 ` Arnd Bergmann
2016-09-09 20:13 ` Kevin Hilman
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=2582793.W17ckCts1B@wuerfel \
--to=arnd@arndb.de \
--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