From: Guenter Roeck <linux@roeck-us.net>
To: Michael Ellerman <mpe@ellerman.id.au>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Scott Wood <oss@buserror.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 14
Date: Mon, 14 Mar 2016 19:31:53 -0700 [thread overview]
Message-ID: <56E77419.1010302@roeck-us.net> (raw)
In-Reply-To: <1457999708.8059.1.camel@ellerman.id.au>
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
next prev parent reply other threads:[~2016-03-15 2:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 6:40 linux-next: Tree for Mar 14 Stephen Rothwell
2016-03-14 14:37 ` Guenter Roeck
2016-03-14 16:51 ` James Morse
2016-03-14 19:18 ` Guenter Roeck
2016-03-14 23:55 ` Michael Ellerman
2016-03-15 2:31 ` Guenter Roeck [this message]
2016-03-15 5:26 ` linux-next: Tree for Mar 14 (mips qemu failure bisected) Guenter Roeck
2016-03-15 21:55 ` Qais Yousef
2016-03-16 0:17 ` Guenter Roeck
2016-03-16 13:22 ` Guenter Roeck
2016-03-16 20:27 ` Qais Yousef
2016-03-16 22:17 ` Qais Yousef
2016-03-17 2:10 ` Guenter Roeck
2016-03-17 2:36 ` Guenter Roeck
[not found] ` <CA+mqd+5AUfGSh1WvLa5bOt-HQM=eA+BmLeb7_xZo+-tswLcqiQ@mail.gmail.com>
2016-03-17 12:43 ` Guenter Roeck
2016-03-15 0:30 ` linux-next: Tree for Mar 14 Sergey Senozhatsky
2016-03-15 6:43 ` Wolfram Sang
2016-03-15 6:52 ` Sergey Senozhatsky
-- strict thread matches above, loose matches on Subject: below --
2024-03-14 3:22 Stephen Rothwell
2023-03-14 3:24 Stephen Rothwell
2018-03-14 6:27 Stephen Rothwell
2014-03-14 19:32 Mark Brown
2013-03-14 7:06 Stephen Rothwell
2012-03-14 7:19 Stephen Rothwell
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=56E77419.1010302@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=oss@buserror.net \
--cc=sfr@canb.auug.org.au \
/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).