From: Greg Ungerer <gerg@linux-m68k.org>
To: torvalds@linux-foundation.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [git pull] m68knommu changes for v5.8-rc4
Date: Fri, 3 Jul 2020 08:21:59 +1000 [thread overview]
Message-ID: <85548a92-b917-08e2-e89c-833bf5cb97b4@linux-m68k.org> (raw)
Hi Linus,
Please pull important m68knommu fixes for v5.8-rc4
Regards
Greg
The following changes since commit 9ebcfadb0610322ac537dd7aa5d9cbc2b2894c68:
Linux 5.8-rc3 (2020-06-28 15:00:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-for-v5.8-rc4
for you to fetch changes up to c43e55796dd4d13f4855971a4d7970ce2cd94db4:
m68k: mm: fix node memblock init (2020-06-29 23:58:05 +1000)
----------------------------------------------------------------
m68knommu: mm fixes needed for v5.8
Two critical mm related fixes that affect booting of m68k/ColdFire devices.
Both fix problems caused by recent system init memblock changes.
----------------------------------------------------------------
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(-)
next reply other threads:[~2020-07-02 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 22:21 Greg Ungerer [this message]
2020-07-03 6:10 ` [git pull] m68knommu changes for v5.8-rc4 pr-tracker-bot
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=85548a92-b917-08e2-e89c-833bf5cb97b4@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@linux-foundation.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).