All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: nommu build failures on ARM in linux-next
Date: Thu, 29 May 2014 12:53:51 -0400	[thread overview]
Message-ID: <5387661F.1050000@windriver.com> (raw)

Hi Russell,

The allnoconfig builds in linux-next fail because __clear_cr
lives in mmu.c without any stub or similar in nommu.c

Introduced by:

commit 247e4fff3aa927ad069447e6da05bb966b70dece
Author: Russell King <rmk+kernel@arm.linux.org.uk>
Date:   Sun Apr 13 18:57:29 2014 +0100

    ARM: provide common method to clear bits in CPU control register
    
Sample failure:
  http://kisskb.ellerman.id.au/kisskb/buildresult/11264405/

Paul.

WARNING: multiple messages have this Message-ID (diff)
From: paul.gortmaker@windriver.com (Paul Gortmaker)
To: linux-arm-kernel@lists.infradead.org
Subject: nommu build failures on ARM in linux-next
Date: Thu, 29 May 2014 12:53:51 -0400	[thread overview]
Message-ID: <5387661F.1050000@windriver.com> (raw)

Hi Russell,

The allnoconfig builds in linux-next fail because __clear_cr
lives in mmu.c without any stub or similar in nommu.c

Introduced by:

commit 247e4fff3aa927ad069447e6da05bb966b70dece
Author: Russell King <rmk+kernel@arm.linux.org.uk>
Date:   Sun Apr 13 18:57:29 2014 +0100

    ARM: provide common method to clear bits in CPU control register
    
Sample failure:
  http://kisskb.ellerman.id.au/kisskb/buildresult/11264405/

Paul.

             reply	other threads:[~2014-05-29 16:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 16:53 Paul Gortmaker [this message]
2014-05-29 16:53 ` nommu build failures on ARM in linux-next Paul Gortmaker
2014-05-29 18:55 ` Russell King - ARM Linux
2014-05-29 18:55   ` Russell King - ARM Linux
2014-05-29 23:40   ` Russell King - ARM Linux
2014-05-29 23:40     ` Russell King - ARM Linux
2014-05-30  0:05     ` Paul Gortmaker
2014-05-30  0:05       ` Paul Gortmaker
2014-05-30  7:58     ` Robert Schwebel
2014-05-30  7:58       ` Robert Schwebel
2014-05-30  8:02     ` Uwe Kleine-König
2014-05-30  8:02       ` Uwe Kleine-König
2014-06-02  7:19       ` Uwe Kleine-König
2014-06-02  7:19         ` Uwe Kleine-König

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=5387661F.1050000@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.