From: Greg Ungerer <gerg@linux-m68k.org>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Sam Creasey <sammy@sammy.net>
Cc: Michal Hocko <mhocko@kernel.org>,
linux-m68k@lists.linux-m68k.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] m68k: switch to MEMBLOCK + NO_BOOTMEM
Date: Thu, 5 Jul 2018 22:13:52 +1000 [thread overview]
Message-ID: <4c08ad85-95f8-7001-5429-eaaf36d061de@linux-m68k.org> (raw)
In-Reply-To: <1530685696-14672-1-git-send-email-rppt@linux.vnet.ibm.com>
Hi Mike,
On 04/07/18 16:28, Mike Rapoport wrote:
> These patches switch m68k boot time memory allocators from bootmem to
> memblock + no_bootmem.
>
> The first two patches update __ffs() and __va() definitions to be inline
> with other arches and asm-generic. This is required to avoid compilation
> warnings in mm/memblock.c and mm/nobootmem.c.
>
> The third patch performs the actual switch of the boot time mm. Its
> changelog has detailed description of the changes.
>
> I've tested the !MMU version with qemu-system-m68k -M mcf5208evb
> and the MMU version with q800 using qemu from [1].
>
> I've also build tested allyesconfig and *_defconfig.
>
> [1] https://github.com/vivier/qemu-m68k.git
>
> v2:
> * fix reservation of the kernel text/data/bss for ColdFire MMU
I am happy with all of these, so for me:
Acked-by: Greg Ungerer <gerg@linux-m68k.org>
Regards
Greg
> Mike Rapoport (3):
> m68k/bitops: convert __ffs to match generic declaration
> m68k/page_no.h: force __va argument to be unsigned long
> m68k: switch to MEMBLOCK + NO_BOOTMEM
>
> arch/m68k/Kconfig | 3 +++
> arch/m68k/include/asm/bitops.h | 8 ++++++--
> arch/m68k/include/asm/page_no.h | 2 +-
> arch/m68k/kernel/setup_mm.c | 14 ++++----------
> arch/m68k/kernel/setup_no.c | 20 ++++----------------
> arch/m68k/mm/init.c | 1 -
> arch/m68k/mm/mcfmmu.c | 13 +++++++------
> arch/m68k/mm/motorola.c | 35 +++++++++++------------------------
> arch/m68k/sun3/config.c | 4 ----
> 9 files changed, 36 insertions(+), 64 deletions(-)
>
next prev parent reply other threads:[~2018-07-05 12:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 6:28 [PATCH v2 0/3] m68k: switch to MEMBLOCK + NO_BOOTMEM Mike Rapoport
2018-07-04 6:28 ` [PATCH v2 1/3] m68k/bitops: convert __ffs to match generic declaration Mike Rapoport
2018-07-04 6:28 ` [PATCH v2 2/3] m68k/page_no.h: force __va argument to be unsigned long Mike Rapoport
2018-07-04 6:28 ` [PATCH v2 3/3] m68k: switch to MEMBLOCK + NO_BOOTMEM Mike Rapoport
2018-07-04 7:44 ` Geert Uytterhoeven
2018-07-04 7:54 ` Michal Hocko
2018-07-04 8:21 ` Geert Uytterhoeven
2018-07-04 12:22 ` Vlastimil Babka
2018-07-04 12:36 ` Michal Hocko
2018-07-04 12:43 ` Mike Rapoport
2018-07-04 12:51 ` Michal Hocko
2018-07-04 12:57 ` Mike Rapoport
2018-07-04 13:05 ` Geert Uytterhoeven
2018-07-04 13:14 ` Michal Hocko
2018-07-06 6:17 ` Michal Hocko
2018-07-05 12:13 ` Greg Ungerer [this message]
2018-07-18 11:39 ` [PATCH v2 0/3] " Geert Uytterhoeven
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=4c08ad85-95f8-7001-5429-eaaf36d061de@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=sammy@sammy.net \
/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).