linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Subject: Re: linux-next: Tree for Nov 13
Date: Thu, 13 Nov 2014 06:11:16 -0800	[thread overview]
Message-ID: <20141113141116.GA15339@roeck-us.net> (raw)
In-Reply-To: <20141113181002.6c583589@canb.auug.org.au>

On Thu, Nov 13, 2014 at 06:10:02PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20141112:
> 
> The net-next tree gained a conflict against the net tree.
> 
> The mfd tree gained a conflict against Linus' tree.
> 
> The akpm-current tree lost its build failures.
> 
> Non-merge commits (relative to Linus' tree): 6008
>  6314 files changed, 193590 insertions(+), 163738 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.
> 
Build results:
	total: 133 pass: 124 fail: 9
Failed builds:
	arm:davinci_all_defconfig
	arm:axm55xx_defconfig
	arm:orion5x_defconfig
	arm:clps711x_defconfig
	blackfin:defconfig
	hexagon:defconfig
	m68k:allmodconfig
	powerpc:ppc6xx_defconfig (binutils 2.23)
	powerpc:ppc6xx_defconfig (binutils 2.24)

Qemu tests:
	total: 30 pass: 29 fail: 1
Failed tests:
	x86:x86_pc_nosmp_defconfig

Details are available at http://server.roeck-us.net:8010/builders.

Guenter

  reply	other threads:[~2014-11-13 14:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13  7:10 linux-next: Tree for Nov 13 Stephen Rothwell
2014-11-13 14:11 ` Guenter Roeck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-13  0:42 Stephen Rothwell
2020-11-13  7:08 Stephen Rothwell
2019-11-13  9:42 Stephen Rothwell
2018-11-13  4:43 Stephen Rothwell
2017-11-13  6:28 Stephen Rothwell
2015-11-13  2:23 Stephen Rothwell
2013-11-13  5:15 Stephen Rothwell
2012-11-13  6:00 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=20141113141116.GA15339@roeck-us.net \
    --to=linux@roeck-us.net \
    --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).