linux-kernel - linux-next: Tree for 3rd December

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-next>] [day] [month] [year] [list]

Date:	Thu, 3 Dec 2015 23:31:43 +0000
From:	Mark Brown <broonie@...nel.org>
To:	linux-next@...r.kernel.org
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-kernel@...r.kernel.org
Subject: linux-next: Tree for 3rd December

Hi all,

Changes since 20151202:

Both of Andrew's trees are included.

The block and gpio trees still have their build failures so I used the
versions from next-20151127.

There were several new conflicts between the drm-intel-fixes and
drm-next trees.

It is very unlikely that there will be a build tomorrow, Stephen will be
back and -next will be back to normal on Monday.

Non-merge commits (relative to Linus' tree): 3709
 5435 files changed, 721155 insertions(+), 627700 deletions(-)

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
If you are tracking the linux-next tree using git, you should not use
"git pull" to do so as that will try to merge the new linux-next release
with the old one.  You should use "git fetch" and checkout or reset to
the new master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a defconfig for arm64 and an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)