From: Russell King - ARM Linux <linux@arm•linux.org.uk>
To: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"linux-arm-kernel@lists•infradead.org"
<linux-arm-kernel@lists•infradead.org>
Subject: Re: nommu build failures on ARM in linux-next
Date: Thu, 29 May 2014 19:55:34 +0100 [thread overview]
Message-ID: <20140529185534.GK3693@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <5387661F.1050000@windriver.com>
On Thu, May 29, 2014 at 12:53:51PM -0400, Paul Gortmaker wrote:
> 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/
ALIGNMENT_TRAP depends on CPU_CP15_MMU, so it's quite reasonable that
__clear_cr should exist in this case - but it doesn't because it's in
mmu.c. I guess we need __clear_cr moved to arch/arm/kernel/setup.c.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-05-29 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 16:53 nommu build failures on ARM in linux-next Paul Gortmaker
2014-05-29 18:55 ` Russell King - ARM Linux [this message]
2014-05-29 23:40 ` Russell King - ARM Linux
2014-05-30 0:05 ` Paul Gortmaker
2014-05-30 7:58 ` Robert Schwebel
2014-05-30 8:02 ` 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=20140529185534.GK3693@n2100.arm.linux.org.uk \
--to=linux@arm$(echo .)linux.org.uk \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.gortmaker@windriver$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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