On Mon, Dec 07, 2015 at 09:54:50AM -0500, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.2.7 release.
> There are 124 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Wed Dec 9 14:48:34 UTC 2015.
> Anything received after that time might be too late.
>
Build results:
total: 145 pass: 140 fail: 5
Failed builds:
arm:allmodconfig
arm:imx_v6_v7_defconfig
arm:omap1_defconfig
s390:defconfig
s390:allmodconfig
Qemu test results:
total: 95 pass: 84 fail: 11
Failed tests:
arm:kzm:imx_v6_v7_defconfig
arm:beagle:multi_v7_defconfig:omap3-beagle
arm:beaglexm:multi_v7_defconfig:omap3-beagle-xm
arm:overo:multi_v7_defconfig:omap3-overo-tobi
arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
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:smdkc210:multi_v7_defconfig:exynos4210-smdkv310
s390:defconfig
On top of the s390 failures, which are the same as for 4.1 and 4.3,
several arm builds fail as follows.
./arch/arm/include/asm/irq.h: Assembler messages:
./arch/arm/include/asm/irq.h:40: Error:
bad instruction `static inline int nr_legacy_irqs(void)'
./arch/arm/include/asm/irq.h:41: Error:
junk at end of line, first unrecognized character is `{'
./arch/arm/include/asm/irq.h:42: Error:
bad instruction `return 16'
./arch/arm/include/asm/irq.h:43: Error:
junk at end of line, first unrecognized character is `}'
Culprit is 'xen/events: Always allocate legacy interrupts on PV guests'.
Function 'static inline int nr_legacy_irqs(void)' is applied outside the
'#ifndef __ASSEMBLY__' conditional, which causes the compile failures.
Details are available at http://server.roeck-us.net:8010/builders.
Guenter
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html