From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable <stable@vger.kernel.org>
Subject: Build errors in v3.18.y.queue
Date: Sat, 3 Nov 2018 07:38:55 -0700 [thread overview]
Message-ID: <bc98562d-a4d6-c0e4-244d-0bb78bc41eb0@roeck-us.net> (raw)
For v3.18.124-131-g7e61c1e8ba56:
Build results:
total: 138 pass: 135 fail: 3
Failed builds:
arm:allmodconfig
arm:omap2plus_defconfig
arm:exynos_defconfig
Qemu test results:
total: 221 pass: 205 fail: 16
Failed tests:
arm:beagle:multi_v7_defconfig:omap3-beagle
arm:beaglexm:multi_v7_defconfig:omap3-beagle-xm
arm:overo:multi_v7_defconfig:omap3-overo-tobi
arm:sabrelite:multi_v7_defconfig:imx6dl-sabrelite
arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
arm:vexpress-a15-a7:multi_v7_defconfig:vexpress-v2p-ca15_a7
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc702
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706
arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zed
arm:cubieboard:multi_v7_defconfig:sun4i-a10-cubieboard
arm:midway:multi_v7_defconfig:ecx-2000
arm:smdkc210:exynos_defconfig:exynos4210-smdkv310
arm:beagle:omap2plus_defconfig:omap3-beagle
arm:beaglexm:omap2plus_defconfig:omap3-beagle-xm
arm:overo:omap2plus_defconfig:omap3-overo-tobi
---
arch/arm/mach-omap2/omap-headsmp.S: Assembler messages:
arch/arm/mach-omap2/omap-headsmp.S:60: Error: bad instruction `badr r0,hyp_boot'
drivers/clocksource/exynos_mct.c: In function 'exynos4_local_timer_stop':
drivers/clocksource/exynos_mct.c:490:26: error: 'mevt' undeclared
Culprits:
59566174aef6 ARM: OMAP5 / DRA7: Fix HYP mode boot for thumb2 build
4042eb2ed0c7 clocksource/exynos_mct: Clear interrupt when cpu is shut down
Guenter
next reply other threads:[~2018-11-03 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 14:38 Guenter Roeck [this message]
2018-11-03 15:28 ` Build errors in v3.18.y.queue Sasha Levin
2019-02-12 16:47 Guenter Roeck
2019-02-12 18:37 ` 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=bc98562d-a4d6-c0e4-244d-0bb78bc41eb0@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=stable@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).