From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Sam Ravnborg <sam@ravnborg.org>, Michal Hocko <mhocko@kernel.org>,
sparclinux@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: [PATCH v2 0/3] sparc32: switch to NO_BOOTMEM
Date: Mon, 6 Aug 2018 13:52:32 +0300 [thread overview]
Message-ID: <1533552755-16679-1-git-send-email-rppt@linux.vnet.ibm.com> (raw)
Hi,
These patches convert sparc32 to use memblock + nobootmem.
I've made the conversion as simple as possible, just enough to allow moving
HAVE_MEMBLOCK and NO_BOOTMEM to the common SPARC configuration.
v2 changes:
* split whitespace changes to a separate patch
* address Sam's comments [1]
[1] https://lkml.org/lkml/2018/8/2/403
Mike Rapoport (3):
sparc: mm/init_32: kill trailing whitespace
sparc32: switch to NO_BOOTMEM
sparc32: split ramdisk detection and reservation to a helper function
arch/sparc/Kconfig | 4 +-
arch/sparc/mm/init_32.c | 127 ++++++++++++++++++------------------------------
2 files changed, 50 insertions(+), 81 deletions(-)
--
2.7.4
next reply other threads:[~2018-08-06 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 10:52 Mike Rapoport [this message]
2018-08-06 10:52 ` [PATCH v2 1/3] sparc: mm/init_32: kill trailing whitespace Mike Rapoport
2018-08-06 10:52 ` [PATCH v2 2/3] sparc32: switch to NO_BOOTMEM Mike Rapoport
2018-08-06 13:08 ` Sam Ravnborg
2018-08-06 10:52 ` [PATCH v2 3/3] sparc32: split ramdisk detection and reservation to a helper function Mike Rapoport
2018-08-06 13:09 ` Sam Ravnborg
2018-08-21 19:40 ` [PATCH v2 0/3] sparc32: switch to NO_BOOTMEM David Miller
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=1533552755-16679-1-git-send-email-rppt@linux.vnet.ibm.com \
--to=rppt@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.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).