lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 14 Mar 2016 19:31:53 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Michael Ellerman <mpe@...erman.id.au>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Scott Wood <oss@...error.net>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: Tree for Mar 14

On 03/14/2016 04:55 PM, Michael Ellerman wrote:
> On Mon, 2016-03-14 at 07:37 -0700, Guenter Roeck wrote:
>> On Mon, Mar 14, 2016 at 05:40:37PM +1100, Stephen Rothwell wrote:
>>
>> To give people an idea what to expect in the merge window, here are my current
>> build and runtime test results. Some of the runtime failures are due to the
>> newly introduced i2c bug, but many (including the arm64 boot failures) have
>> been around for a while.
>>
>> Qemu test results:
>> 	total: 96 pass: 69 fail: 27
>> Failed tests:
> ...
>> 	powerpc:mpc8544ds:mpc85xx_smp_defconfig
>> 	powerpc:mpc8544ds:mpc85xx_defconfig
>> 	powerpc:smp:ppc64_e5500_defconfig
>
> These are all an i2c crash, which I assume is the one you mention above.
>
>> 	powerpc:nosmp:ppc64_e5500_defconfig
>
> This seems to be caused by:
>
>    arch/powerpc/sysdev/fsl_rcpm.c:32:2: error: implicit declaration of function 'get_hard_smp_processor_id' [-Werror=implicit-function-declaration]
>
> ie. that driver doesn't build for SMP=n.
>

Maybe it should include <asm/smp.h> to get the UP definition.

Guenter

Powered by blists - more mailing lists