From: Guenter Roeck <linux@roeck-us.net>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: v4.18-rc3: Build and qemu test results
Date: Mon, 2 Jul 2018 09:47:58 -0700 [thread overview]
Message-ID: <20180702164758.GA9835@roeck-us.net> (raw)
In-Reply-To: <20180702164605.GF9114@roeck-us.net>
[trying again, this time to a valid address]
Build and qemu test results for v4.18-rc3:
Build results:
total: 134 pass: 128 fail: 6
Failed builds:
arm:allmodconfig
i386:allyesconfig
i386:allmodconfig
nds32:defconfig
nds32:allnoconfig
sparc32:allmodconfig
Qemu test results:
total: 158 pass: 158 fail: 0
---
arm:allmodconfig:
/tmp/ccXj8hfB.s: Assembler messages:
/tmp/ccXj8hfB.s:35: Error: .err encountered
/tmp/ccXj8hfB.s:36: Error: .err encountered
/tmp/ccXj8hfB.s:37: Error: .err encountered
make[2]: *** [arch/arm/firmware/trusted_foundations.o] Error 1
Fix at:
https://patchwork.kernel.org/patch/10434909/
[not queued in -next]
---
i386:allyesconfig, i386:allmodconfig:
x86_64-linux-ld: i386:x86-64 architecture of input file
`net/bpfilter/bpfilter_umh.o' is incompatible with i386 output
next-20180702 builds fine, so presumably the fix is queued there.
---
nds32:defconfig, nds32:allnoconfig:
nds32le-linux-ld: kernel/time/timekeeping.o: in function `timekeeping_init':
timekeeping.c:(.init.text+0x1a8): undefined reference to `__ashldi3'
nds32le-linux-ld: timekeeping.c:(.init.text+0x1ac):
undefined reference to `__ashldi3'
nds32le-linux-ld: timekeeping.c:(.init.text+0x1ec):
undefined reference to `__lshrdi3'
nds32le-linux-ld: timekeeping.c:(.init.text+0x1f0):
undefined reference to `__lshrdi3'
nds32le-linux-ld: fs/direct-io.o: in function `do_direct_IO':
direct-io.c:(.text+0x16a0): undefined reference to `__ashldi3'
Fix is queued in -next.
---
sparc32:allmodconfig:
...
drivers/staging/media/omap4iss/iss_video.c:15:
build/include/linux/highmem.h: In function 'clear_user_highpage':
include/linux/highmem.h:137:31: error:
passing argument 1 of 'sparc_flush_page_to_ram' from incompatible pointer type
This is only seen with gcc 5 and later; gcc 4 produces warnings.
Building drivers/staging/media/omap4iss/iss_video.c for sparc32 was only
recently enabled with COMPILE_TEST. A possible fix for the problem is
available at https://patchwork.kernel.org/patch/10497941/.
Further details are available at http://kerneltests.org/builders.
Guenter
next parent reply other threads:[~2018-07-02 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180702164605.GF9114@roeck-us.net>
2018-07-02 16:47 ` Guenter Roeck [this message]
2018-07-02 16:52 ` Linus Torvalds
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=20180702164758.GA9835@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®