Re: [PATCH 3.4 000/176] 3.4.107-rc1 review
From: Zefan Li
Date: Sun Apr 12 2015 - 22:02:08 EST
> Build results:
> total: 105 pass: 86 fail: 19
> Failed builds:
> arm:omap1_defconfig
> arm:at91rm9200_defconfig
> i386:allyesconfig
> mips:defconfig
> mips:allmodconfig
> mips:bcm47xx_defconfig
> mips:bcm63xx_defconfig
> mips:nlm_xlp_defconfig
> mips:ar7_defconfig
> mips:fuloong2e_defconfig
> mips:e55_defconfig
> mips:powertv_defconfig
> mips:malta_defconfig
> s390:defconfig
> score:defconfig
> sparc64:allmodconfig
> tile:tilegx_defconfig
> x86_64:allyesconfig
> xtensa:allmodconfig
>
> Qemu test results:
> total: 23 pass: 14 fail: 9
> Failed tests:
> arm:arm_versatile_defconfig
> mips:mips_malta_defconfig
> mips:mips_malta_smp_defconfig
> mips:mipsel_malta_defconfig
> mips:mipsel_malta_smp_defconfig
> mips64:mips_malta64_defconfig
> mips64:mips_malta64_smp_defconfig
> x86:x86_pc_defconfig
> x86:x86_pc_nosmp_defconfig
>
> Unexpected build errors:
>
> drivers/usb/serial/console.c: In function 'usb_console_setup':
> drivers/usb/serial/console.c:151:4: error: expected ';' before 'if'
>
> ---
> arch/mips/mm/tlb-r4k.c: In function 'tlb_init':
> arch/mips/mm/tlb-r4k.c:413:7: error: 'cpu_has_rixiex' undeclared (first use in this function)
> arch/mips/mm/tlb-r4k.c:414:10: error: 'PG_IEC' undeclared (first use in this function)
>
> ---
> arch/s390/mm/fault.c: In function 'do_fault_error':
> arch/s390/mm/fault.c:243:25: error: 'int_code' undeclared (first use in this function)
> arch/s390/mm/fault.c:243:35: error: 'trans_exc_code' undeclared (first use in this function)
> arch/s390/mm/fault.c:243:5: error: too many arguments to function 'do_no_context'
> arch/s390/mm/fault.c:159:22: note: declared here
> arch/s390/mm/fault.c:246:9: error: too many arguments to function 'do_sigsegv'
> arch/s390/mm/fault.c:148:22: note: declared here
>
> Let me know if you need me to bisect.
>
Thanks for testing.
All should be fixed. Could you give it another try?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/