Stephen Rowell wrote on Mon, Jul 7, 2014 at 2:42 AM
Subject: linux-next: Tree for Jul 7
To: linux-next@xxxxxxxxxxxxxxx
Cc:linux-next@xxxxxxxxxxxxxxx
Hi all,
Changes since 20140704:
My fixes tree contains:
powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
The net tree still had its build failure for which I reverted a commit.
The mvebu tree gained a conflict against the arm tree.
The renesas tree gained a conflict against the arm tree.
The staging tree still had its build failure for which I disabled a driver.
The akpm-current tree still had its build failure for which I applied a
patch.
Non-merge commits (relative to Linus' tree): 3683
3559 files changed, 139800 insertions(+), 187348 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@xxxxxxxxxxxxxxxx
I am testing your tests again for the failing cases. Below is my list
of what failing tests
are pasting for me and which are still failing.
Cheers Nick
Arm - All succeed
Blackfin - BF561-ACVILON_defconfig fails , BlackStamp_defconfig Fails
, TCM-BF518_defconfig succeeds
Cris - cris-allmodconfig fails ,cris-allyesconfig fails
or32 -no compiler
powerpc - allyesconfig fails without a patch I have sent to maintainer
of this arch
s390 - s390-allnoconfig succeeds
sh4- rsk7203_defconfig fails, se7722_defconfig succeeds,
shx3_defconfig fails ,ecovec24-romimage_defconfig succeeds
,kfr2r09-romimage_defconfig succeeds,
kfr2r09_defconfig succeeds , sh7724_generic_defconfig succeeds,
sh7770_generic_defconfig succeeds, sh-allmodconfig fails,
sh-allyesconfig fails
Sparc64 - sparc-allmodconfig seems to pass
1386-um - um-defconfig succeeds
In addition you seem to be using a very old toolchain gcc 4.2.3 I
would upgrade as that
may be an issue.
Cheers Nick
Attachment:
signature.asc
Description: PGP signature
