From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Nov 26
Date: Wed, 26 Nov 2014 18:52:38 -0800 [thread overview]
Message-ID: <20141127025238.GA18150@roeck-us.net> (raw)
In-Reply-To: <20141126233827.3353c3f4@canb.auug.org.au>
On Wed, Nov 26, 2014 at 11:38:27PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20141125:
>
> The i2c tree lost its build failure.
>
> The block tree gained a conflict against the ext4 tree.
>
> The omap_dss2 tree still had its build failure for which I applied a patch.
>
> The devicetree tree gained conflicts against the i2c, pm, mfd and
> regulator trees.
>
> The kvm-arm tree gained a conflict against the kvm tree.
>
> The tty tree gained a conflict against the tty.current tree.
>
> Non-merge commits (relative to Linus' tree): 8617
> 8299 files changed, 317805 insertions(+), 228360 deletions(-)
>
Builds results:
total: 133 pass: 126 fail: 7
Failed builds:
alpha:allmodconfig
arm:orion5x_defconfig
arm:cm_x2xx_defconfig
hexagon:defconfig
sparc64:allmodconfig
x86_64:allyesconfig
xtensa:allmodconfig
Qemu tests:
total: 30 pass: 22 fail: 8
Failed tests:
arm:arm_versatile_defconfig
mips:mips_malta_defconfig
mips:mipsel_malta_defconfig
mips:mipsel_malta_smp_defconfig
powerpc:ppc_book3s_defconfig
powerpc:ppc_book3s_smp_defconfig
powerpc:ppc64_book3s_defconfig
powerpc:ppc64_book3s_smp_defconfig
As far as I can see, qemu failures are all due to build failures
due to
ERROR: "nf_nat_redirect_ipv6" [net/netfilter/xt_REDIRECT.ko] undefined!
Details at http://server.roeck-us.net:8010/builders.
Guenter
next prev parent reply other threads:[~2014-11-27 2:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 12:38 linux-next: Tree for Nov 26 Stephen Rothwell
2014-11-27 2:52 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-26 5:22 Stephen Rothwell
2020-11-26 8:05 Stephen Rothwell
2019-11-26 6:28 Stephen Rothwell
2018-11-26 9:03 Stephen Rothwell
2015-11-26 5:16 Stephen Rothwell
2013-11-26 3:42 Stephen Rothwell
2012-11-26 14:17 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=20141127025238.GA18150@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).