From: Mike Rapoport <rppt@linux.vnet.ibm.com>
Date: Mon, 20 Aug 2018 05:25:37 +0000 (+0300)
Subject: m68k: fix early memory reservation for ColdFire MMU systems
X-Git-Tag: v4.19~230^2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=c90bbce9eedd14f9428388d9442b5b3e98a2a6dd;p=platform%2Fkernel%2Flinux-rpi.git

m68k: fix early memory reservation for ColdFire MMU systems

The bootmem to memblock conversion introduced by the commit 1008a11590b9
("m68k: switch to MEMBLOCK + NO_BOOTMEM") made reservation of kernel code
and data to start from a wrong address.

Fix it.

Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
Tested-by: Angelo Dureghello <angelo@sysam.it>
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
---

diff --git a/arch/m68k/mm/mcfmmu.c b/arch/m68k/mm/mcfmmu.c
index 70dde04..f5453d9 100644
--- a/arch/m68k/mm/mcfmmu.c
+++ b/arch/m68k/mm/mcfmmu.c
@@ -172,7 +172,7 @@ void __init cf_bootmem_alloc(void)
 	high_memory = (void *)_ramend;
 
 	/* Reserve kernel text/data/bss */
-	memblock_reserve(memstart, memstart - _rambase);
+	memblock_reserve(_rambase, memstart - _rambase);
 
 	m68k_virt_to_node_shift = fls(_ramend - 1) - 6;
 	module_fixup(NULL, __start_fixup, __stop_fixup);