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,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: linux-next: Tree for Aug 28
Date: Fri, 28 Aug 2015 08:24:41 -0700 [thread overview]
Message-ID: <20150828152441.GA8179@roeck-us.net> (raw)
In-Reply-To: <20150828182712.3d45a033@canb.auug.org.au>
On Fri, Aug 28, 2015 at 06:27:12PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150827:
>
> The rdma tree gained a conflict aaginst the net-next tree.
>
> The sound-asoc tree gained a build failure for which I reverted a commit.
>
> The mmc-uh tree lost its build failure.
>
> The tty tree still had its build failure for which I reverted part of
> a commit.
>
> The nvdimm tree gained conflicts against Linus' and the v4l-dvb trees.
>
> Non-merge commits (relative to Linus' tree): 10211
> 8743 files changed, 533186 insertions(+), 210999 deletions(-)
>
> ----------------------------------------------------------------------------
>
Time for a status report. We might see at least some of the following
failures in mainline after the commit window closes.
Build results:
total: 145 pass: 138 fail: 7
Failed builds:
alpha:allmodconfig [1], [2]
arm:rpc_defconfig [3]
mips:nlm_xlp_defconfig [4]
s390:allmodconfig [5]
xtensa:defconfig [6]
xtensa:allmodconfig [6]
xtensa:allnoconfig [6]
Qemu test results:
total: 85 pass: 80 fail: 5
Failed tests:
mips:fuloong2e_defconfig [7]
xtensa:dc232b:lx60:xtensa_defconfig [6]
xtensa:dc232b:kc705:xtensa_defconfig [6]
xtensa:dc233c:ml605:generic_kc705_defconfig [6]
xtensa:dc233c:kc705:generic_kc705_defconfig [6]
Guenter
---
[1] new, introduced by "libnvdimm, pfn: 'struct page' provider infrastructure"
[2] https://lkml.org/lkml/2015/7/31/1373
[3] https://lkml.org/lkml/2015/8/26/462
[4] http://patchwork.linux-mips.org/patch/11054/
[5] https://lkml.org/lkml/2015/8/26/744
[6] https://lkml.org/lkml/2015/8/26/118
[7] http://patchwork.linux-mips.org/patch/10896/
next prev parent reply other threads:[~2015-08-28 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 8:27 linux-next: Tree for Aug 28 Stephen Rothwell
2015-08-28 15:24 ` Guenter Roeck [this message]
2015-08-28 19:06 ` Dan Williams
-- strict thread matches above, loose matches on Subject: below --
2023-08-28 5:02 Stephen Rothwell
2020-08-28 5:23 Stephen Rothwell
2019-08-28 10:02 Stephen Rothwell
2018-08-28 1:24 Stephen Rothwell
2017-08-28 9:31 Stephen Rothwell
2014-08-28 5:46 Stephen Rothwell
2013-08-28 8:45 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=20150828152441.GA8179@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dan.j.williams@intel.com \
--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).