From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: avoid ARCH_MMAP_RND_BITS for NOMMU
Date: Fri, 27 Nov 2015 15:04:03 +0100 [thread overview]
Message-ID: <2874133.c4GDUf0t6t@wuerfel> (raw)
ARM kernels with MMU disabled fail to build because of CONFIG_ARCH_MMAP_RND_BITS:
kernel/built-in.o:(.data+0x754): undefined reference to `mmap_rnd_bits'
kernel/built-in.o:(.data+0x76c): undefined reference to `mmap_rnd_bits_min'
kernel/built-in.o:(.data+0x770): undefined reference to `mmap_rnd_bits_max'
This changes the newly added line to only select this allow for
MMU-enabled kernels.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Fixes: 14570b3fd31a ("arm: mm: support ARCH_MMAP_RND_BITS")
---
Found on yesterday's linux-next with ARM randconfig. The commit that
introduced this is currently in Andrew's tree.
If you don't already have a fix, please either apply this patch on top,
or fold it into the original patch.
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index b64f64d124c4..5a0957e3ea36 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -34,7 +34,7 @@ config ARM
select HAVE_ARCH_BITREVERSE if (CPU_32v7M || CPU_32v7) && !CPU_32v6
select HAVE_ARCH_JUMP_LABEL if !XIP_KERNEL && !CPU_ENDIAN_BE32 && MMU
select HAVE_ARCH_KGDB if !CPU_ENDIAN_BE32 && MMU
- select HAVE_ARCH_MMAP_RND_BITS
+ select HAVE_ARCH_MMAP_RND_BITS if MMU
select HAVE_ARCH_SECCOMP_FILTER if (AEABI && !OABI_COMPAT)
select HAVE_ARCH_TRACEHOOK
select HAVE_BPF_JIT
next reply other threads:[~2015-11-27 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 14:04 Arnd Bergmann [this message]
2015-11-30 23:40 ` [PATCH] ARM: avoid ARCH_MMAP_RND_BITS for NOMMU Daniel Cashman
2015-12-07 7:21 ` 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=2874133.c4GDUf0t6t@wuerfel \
--to=arnd@arndb.de \
--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).