linux-kernel - Re: linux-next: Tree for Aug 28

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPcyv4iWFGKOLd0KJQRBR9_bG1czoiA_edpoeS5WXtWf_SD9XA@mail.gmail.com>
Date:	Fri, 28 Aug 2015 12:06:46 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Aug 28

On Fri, Aug 28, 2015 at 8:24 AM, Guenter Roeck <linux@...ck-us.net> wrote:
> 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]

Thanks for the report!  Fixed and pushed back out to the
libnvdimm-for-next branch of nvdimm.git
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/