From: Guenter Roeck <linux@roeck-us.net>
To: Stafford Horne <shorne@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"arnd@arndb.de" <arnd@arndb.de>,
Kees Cook <keescook@chromium.org>,
Tony Lindgren <tony@atomide.com>,
Marcin Niestroj <m.niestroj@grinn-global.com>,
Lee Jones <lee.jones@linaro.org>,
Paul Burton <paul.burton@imgtec.com>,
Ralf Baechle <ralf@linux-mips.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: v4.9-rc1: Build and qemu test results (3 build failures, 9 qemu test failures)
Date: Sun, 16 Oct 2016 08:44:11 -0700 [thread overview]
Message-ID: <c2b38067-d459-8f02-04fc-e0aa226dd6f0@roeck-us.net> (raw)
In-Reply-To: <alpine.LFD.2.20.1610162127300.3778@lianli.shorne-pla.net>
On 10/16/2016 05:30 AM, Stafford Horne wrote:
>
>
> On Sat, 15 Oct 2016, Guenter Roeck wrote:
>
>> Here are some build and qemu test results for v4.9-rc1.
>> Details are available at http://kerneltests.org/builders/.
>>
>> Build results:
>> total: 149 pass: 146 fail: 3
>> Failed builds:
>> arm:allmodconfig
>> arm64:allmodconfig
>> powerpc:allmodconfig
>>
>> Qemu test results:
>> total: 110 pass: 101 fail: 9
>> Failed tests:
>> mips: malta_defconfig:nosmp
>> mips: malta_defconfig:smp
>> mips64: malta_defconfig:nosmp
>> mips64: malta_defconfig:smp
>> mipsel: malta_defconfig:nosmp
>> mipsel: malta_defconfig:smp
>> mipsel64: malta_defconfig:nosmp
>> mipsel64: malta_defconfig:smp
>> openrisc:or1ksim_defconfig
>
> For openrisc,
>
> I reproduced this. It seems the fix is a patch you have already posted
> for doing `#define __ro_after_init __read_mostly`. Bisected to commit d2ec3f77de8e ("pty: make ptmx file ops read-only
> after init").
>
> That patch has not made into into the 4.9 tree it seems. Do you have
> a place you can get it in?
>
If Andrew doesn't pick it up, I'll send it to Linus myself
later in the release cycle.
Guenter
>> The build errors are all due to
>> ERROR: "irq_set_parent" [drivers/mfd/tps65217.ko] undefined!
>> Proposed fixes: [1] [2]
>>
>> The qemu/mips failures are fixed with [3], [4].
>> The openrisc qemu failure is fixed with [5].
>>
>> Guenter
>>
>> -------------
>> [1] https://patchwork.kernel.org/patch/9377491/
>> [2] https://patchwork.kernel.org/patch/9330925/
>> [3] https://patchwork.linux-mips.org/patch/14395/
>> [4] https://patchwork.linux-mips.org/patch/14396/
>> [5] https://patchwork.kernel.org/patch/9349191/
>>
>>
>
next prev parent reply other threads:[~2016-10-16 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 6:32 v4.9-rc1: Build and qemu test results (3 build failures, 9 qemu test failures) Guenter Roeck
2016-10-16 12:30 ` Stafford Horne
2016-10-16 15:44 ` Guenter Roeck [this message]
2016-10-24 10:19 ` Lee Jones
2016-10-24 13:03 ` Guenter Roeck
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=c2b38067-d459-8f02-04fc-e0aa226dd6f0@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.niestroj@grinn-global.com \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=shorne@gmail.com \
--cc=tony@atomide.com \
--cc=torvalds@linux-foundation.org \
/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).