linux-kernel - [PATCH] m32r: remove check for CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <1400355184.23222.22.camel@x220>
Date:	Sat, 17 May 2014 21:33:04 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Hirokazu Takata <takata@...ux-m32r.org>
Cc:	linux-m32r@...linux-m32r.org, linux-m32r-ja@...linux-m32r.org,
	linux-kernel@...r.kernel.org
Subject: [PATCH] m32r: remove check for CONFIG_MEMHOLE

There's been a check for CONFIG_MEMHOLE in m32r's code ever since it was
added in v2.6.9. But there has never been a Kconfig symbol MEMHOLE.
(Neither have there been Kconfig symbols MEMHOLE_START and
MEMHOLE_SIZE, by the way.) Remove this check.

Signed-off-by: Paul Bolle <pebolle@...cali.nl>
---
Untested.

 arch/m32r/kernel/setup.c | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/arch/m32r/kernel/setup.c b/arch/m32r/kernel/setup.c
index 0392112a5d70..4975c4555fe8 100644
--- a/arch/m32r/kernel/setup.c
+++ b/arch/m32r/kernel/setup.c
@@ -186,14 +186,6 @@ static unsigned long __init setup_memory(void)
 	 */
 	reserve_bootmem(CONFIG_MEMORY_START, PAGE_SIZE, BOOTMEM_DEFAULT);
 
-	/*
-	 * reserve memory hole
-	 */
-#ifdef CONFIG_MEMHOLE
-	reserve_bootmem(CONFIG_MEMHOLE_START, CONFIG_MEMHOLE_SIZE,
-			BOOTMEM_DEFAULT);
-#endif
-
 #ifdef CONFIG_BLK_DEV_INITRD
 	if (LOADER_TYPE && INITRD_START) {
 		if (INITRD_START + INITRD_SIZE <= (max_low_pfn << PAGE_SHIFT)) {
-- 
1.9.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/