From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 11
Date: Thu, 11 Oct 2018 06:27:16 -0700 [thread overview]
Message-ID: <20181011132716.GA18892@roeck-us.net> (raw)
In-Reply-To: <20181011162343.17787168@canb.auug.org.au>
On Thu, Oct 11, 2018 at 04:23:43PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20181010:
>
> The crypto tree gained conflicts against the mac80211-next tree.
>
> Non-merge commits (relative to Linus' tree): 9625
> 9096 files changed, 465434 insertions(+), 197078 deletions(-)
>
> ----------------------------------------------------------------------------
>
Build results:
total: 135 pass: 123 fail: 12
Failed builds:
alpha:allmodconfig
arm64:allmodconfig
m68k:defconfig
m68k:allmodconfig
mips:allmodconfig
parisc:allmodconfig
powerpc:allmodconfig
powerpc:ppc6xx_defconfig
riscv:defconfig
s390:allmodconfig
sparc64:allmodconfig
xtensa:allmodconfig
Qemu test results:
total: 318 pass: 277 fail: 41
Failed tests:
arm:palmetto-bmc:aspeed_g4_defconfig:aspeed-bmc-opp-palmetto
arm:romulus-bmc:aspeed_g5_defconfig:aspeed-bmc-opp-romulus
...
[39 more]
In addition to yesterday's failures, the above two qemu tests crash
silently, ie without console log. That means they crash before the
console is activated and I have not figured out how to get earlycon
to work.
Guenter
next prev parent reply other threads:[~2018-10-11 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 5:23 linux-next: Tree for Oct 11 Stephen Rothwell
2018-10-11 13:27 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-11 6:25 Stephen Rothwell
2022-10-11 1:49 Stephen Rothwell
2021-10-11 7:37 Stephen Rothwell
2019-10-11 4:05 Stephen Rothwell
2016-10-11 3:06 Stephen Rothwell
2013-10-12 17:21 Mark Brown
2012-10-11 3:06 Stephen Rothwell
2011-10-11 9:11 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=20181011132716.GA18892@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).