From: Mike Rapoport <rppt@kernel.org>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>
Subject: [PATCH 0/2] m68k: fixups for recent changes in memory initialization
Date: Wed, 17 Jun 2020 09:53:39 +0300 [thread overview]
Message-ID: <20200617065341.32160-1-rppt@kernel.org> (raw)
From: Mike Rapoport <rppt@linux.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
next reply other threads:[~2020-06-17 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 6:53 Mike Rapoport [this message]
2020-06-17 6:53 ` [PATCH 1/2] m68k: nommu: register start of the memory with memblock Mike Rapoport
2020-06-17 12:33 ` Greg Ungerer
2020-06-29 1:10 ` Greg Ungerer
2020-06-29 4:14 ` Mike Rapoport
2020-06-29 14:03 ` Greg Ungerer
2020-06-17 6:53 ` [PATCH 2/2] m68k: mm: fix node memblock init Mike Rapoport
2020-06-17 12:34 ` Greg Ungerer
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=20200617065341.32160-1-rppt@kernel.org \
--to=rppt@kernel.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=rppt@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.