linux-kernel.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 20
Date: Thu, 20 Nov 2014 06:46:47 -0800	[thread overview]
Message-ID: <20141120144647.GA6022@roeck-us.net> (raw)
In-Reply-To: <20141120184653.7c7764ac@canb.auug.org.au>

On Thu, Nov 20, 2014 at 06:46:53PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20141119:
> 
> The asm-generic tree lost its build failure.
> 
> The omap_dss2 tree still had its build failure for which I applied a patch.
> 
> The devicetree tree gained a conflict against the devicetree-current tree.
> 
> Non-merge commits (relative to Linus' tree): 7146
>  7140 files changed, 242712 insertions(+), 180038 deletions(-)
> 
> ----------------------------------------------------------------------------
> 
Build results:
	total: 133 pass: 130 fail: 3
Failed builds:
	arm:davinci_all_defconfig
	arm:orion5x_defconfig
	hexagon:defconfig

Qemu test results:
	total: 30 pass: 30 fail: 0

I assume the arm architecture folks will take care of the arm build failures,
so I did not have a look into those. The hexagon build failure is due to a
subtle change in files includes by other include files, resulting in a nested
dependency which is no longer met. That may be tricky to fix.

The qemu x86:nonsmp test only passes because I disabled PCI_MSI for this test.
Claim there is that qemu would not implement some IO_APIC related functionality
which is now mandatory.

Guenter

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20  7:46 Stephen Rothwell
2014-11-20 14:46 ` Guenter Roeck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-20  5:56 Stephen Rothwell
2020-11-20 11:57 ` Sudip Mukherjee
2020-11-20 13:41   ` Thomas Bogendoerfer
2019-11-20  9:34 Stephen Rothwell
2019-11-20 11:22 ` Naresh Kamboju
2018-11-20  5:02 Stephen Rothwell
2017-11-20  3:45 Stephen Rothwell
2015-11-20  4:17 Stephen Rothwell
2013-11-20  2:28 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=20141120144647.GA6022@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 \
    --subject='Re: linux-next: Tree for Nov 20' \
    /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

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).