linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Philippe.Brucker@arm.com (Jean-Philippe Brucker)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20160222 build: 5 failures 9 warnings (next-20160222)
Date: Mon, 22 Feb 2016 10:37:26 +0000	[thread overview]
Message-ID: <20160222103725.GA5163@e106794-lin.cambridge.arm.com> (raw)
In-Reply-To: <20160222102542.GZ18327@sirena.org.uk>

Mark,

On Mon, Feb 22, 2016 at 07:25:42PM +0900, Mark Brown wrote:
> On Mon, Feb 22, 2016 at 08:36:46AM +0000, Build bot for Mark Brown wrote:
> 
> For the past few days -next has been failing to build an arm
> allmodconfig due to:
> 
> > 	arm-allmodconfig
> > ../arch/arm/kernel/hyp-stub.S:168: Error: selected processor does not support ARM mode `ubfx r7,r7,#28,#4'
> > ../arch/arm/kernel/hyp-stub.S:176: Error: selected processor does not support ARM mode `isb'
> 
> caused by e59941b9b3817c (ARM: 8527/1: virt: enable GICv3 system
> registers) in the ARM tree.  My hot take is that it looks like
> CONFIG_ARM_GIC_V3 needs tighter dependencies so it can't get enabled for
> a v6 system but I could be wrong.

Thanks for the report. A fix is already in Russell's patch system [1],
and should be applied shortly.

Thanks,
Jean-Philippe

[1] http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8534/1

      reply	other threads:[~2016-02-22 10:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1aXlz4-000486-Pb@optimist>
2016-02-22 10:08 ` next-20160222 build: 5 failures 9 warnings (next-20160222) Mark Brown
2016-02-22 10:41   ` Marc Zyngier
2016-02-22 11:52     ` Brian Starkey
2016-02-22 12:00       ` Marc Zyngier
2016-02-22 12:07         ` Brian Starkey
2016-02-22 12:44           ` Marc Zyngier
2016-02-22 13:19             ` Stephen Rothwell
2016-02-24  3:28     ` Mark Brown
2016-02-24  3:48       ` Stephen Rothwell
2016-02-24  4:16         ` Mark Brown
2016-02-22 10:19 ` Mark Brown
2016-02-22 10:25 ` Mark Brown
2016-02-22 10:37   ` Jean-Philippe Brucker [this message]

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=20160222103725.GA5163@e106794-lin.cambridge.arm.com \
    --to=jean-philippe.brucker@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).