[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200617065341.32160-1-rppt@kernel.org>
Date: Wed, 17 Jun 2020 09:53:39 +0300
From: Mike Rapoport <rppt@...nel.org>
To: Greg Ungerer <gerg@...ux-m68k.org>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org,
Mike Rapoport <rppt@...nel.org>,
Mike Rapoport <rppt@...ux.ibm.com>
Subject: [PATCH 0/2] m68k: fixups for recent changes in memory initialization
From: Mike Rapoport <rppt@...ux.ibm.com>
Hi,
It's a followup to the Greg's [1] and Angelo's [2] reports of boot problems
caused by the recent rework of the memory initialization.
I'm resending Angelo's original patch for mcfmmu and my fix for the nommu
variant.
[1] https://lore.kernel.org/lkml/f53e68db-ed81-6ef6-5087-c7246d010ea2@linux-m68k.org
[2] https://lore.kernel.org/linux-m68k/20200614225119.777702-1-angelo.dureghello@timesys.com
Angelo Dureghello (1):
m68k: mm: fix node memblock init
Mike Rapoport (1):
m68k: nommu: register start of the memory with memblock
arch/m68k/kernel/setup_no.c | 3 ++-
arch/m68k/mm/mcfmmu.c | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.26.2
Powered by blists - more mailing lists