linux-kernel - Fwd: linux-next: Tree for Jul 9

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

Message-ID: <CAPDOMVjAMHOhuzfcJRL_JQ1jSKOeE7PEhppZJKJKbtR2-ixi-A@mail.gmail.com>
Date:	Wed, 9 Jul 2014 13:07:18 -0400
From:	Nick Krause <xerofoify@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>
Subject: Fwd: linux-next: Tree for Jul 9

---------- Forwarded message ----------
From: Stephen Rothwell wrote on Wed, Jul 9, 2014 at 4:31 AM
Subject: linux-next: Tree for Jul 9
To: linux-next@...r.kernel.org
Cc: linux-kernel@...r.kernel.org

Hi all,

Changes since 20140708:

My fixes tree contains:
        powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64

The net tree lost its build failure.

The net-next tree gained a build failure so I used the version from
next-20140708.

The drm tree gained a conflict against the drm-intel-fixes tree.

The regulator tree lost its build failure.

The iommu tree lost its build failure.

The staging tree still had its build failure for which I disabled a driver.

The rd-docs tree gained a conflict against the trivial tree.

The akpm-current tree still had its build failure for which I applied a
patch.

Non-merge commits (relative to Linus' tree): 4287
 4000 files changed, 161994 insertions(+), 195983 deletions(-)

----------------------------------------------------------------------------

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  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 ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a
multi_v7_defconfig for arm. After the final fixups (if any), it is also
built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and
allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm
defconfig.

Below is a summary of the state of the merge.

I am currently merging 222 trees (counting Linus' and 30 trees of patches
pending for Linus' tree).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

--
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Hey Stephen,

A lot of your builds that are failing seem to build for me. Please try
a compiler toolchain
newer then gcc 4.6.3 to see if this is why your builds are failing.
Since all the arm builds
you have failing build for me.
Cheers Nick

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