Subject: Re: linux-next: Tree for Jan 20

From: Guenter Roeck <[email-masked]>
Date: Tue, 20 Jan 2015 06:16:44 -0800

On Tue, Jan 20, 2015 at 06:53:08PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20150119:
> 
> The omap tree gained a conflict against the arm-soc tree.
> 
> The net-next tree lost its build failure.
> 
> The mmc-uh tree gained a conflict against the sunxi tree.
> 
> The audit tree gained conflicts against Linus' tree.
> 
> Non-merge commits (relative to Linus' tree): 3975
>  3828 files changed, 141642 insertions(+), 68217 deletions(-)
> 
What difference a few days can make ... from zero failures to:

Build results:
	total: 133 pass: 123 fail: 10
Failed builds:
	i386:allyesconfig
	mips:allmodconfig
	powerpc:cell_defconfig (binutils 2.23)
	powerpc:mpc85xx_defconfig
	powerpc:mpc85xx_smp_defconfig
	powerpc:cell_defconfig (binutils 2.24)
	powerpc:mpc85xx_defconfig
	powerpc:mpc85xx_smp_defconfig
	sparc64:allmodconfig
	x86_64:allyesconfig

Qemu tests:
	total: 30 pass: 19 fail: 11
Failed tests:
	microblaze:microblaze_defconfig
	microblaze:microblazeel_defconfig
	mips:mips_malta_smp_defconfig
	mips64:mips_malta64_smp_defconfig
	powerpc:ppc_book3s_smp_defconfig
	powerpc:ppc64_book3s_smp_defconfig
	sh:sh_defconfig
	sparc32:sparc_defconfig
	sparc32:sparc_smp_defconfig
	x86:x86_pc_defconfig
	x86_64:x86_64_pc_defconfig

Most of it mm related problems inherited from mmotm, but there are
a few others (sparc64, x86_64, and i386 don't fail to build on mmotm,
and the microblaze qemu test fails differently, for example).

Guenter