From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Tony Luck <tony.luck@intel.com>, Fenghua Yu <fenghua.yu@intel.com>
Cc: Michal Hocko <mhocko@kernel.org>,
linux-ia64@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: [PATCH 0/4] ia64: switch to NO_BOOTMEM
Date: Mon, 23 Jul 2018 08:56:54 +0300 [thread overview]
Message-ID: <1532325418-22617-1-git-send-email-rppt@linux.vnet.ibm.com> (raw)
Hi,
These patches convert ia64 to use NO_BOOTMEM.
The first two patches are cleanups, the third patches reduces usage of
'struct bootmem_data' for easier transition and the forth patch actually
replaces bootmem with memblock + nobootmem.
I've tested the sim_defconfig with the ski simulator and build tested other
defconfigs.
Mike Rapoport (4):
ia64: contig/paging_init: reduce code duplication
ia64: remove unused num_dma_physpages member from 'struct early_node_data'
ia64: use mem_data to detect nodes' minimal and maximal PFNs
ia64: switch to NO_BOOTMEM
arch/ia64/Kconfig | 1 +
arch/ia64/kernel/setup.c | 11 +++-
arch/ia64/mm/contig.c | 75 +++-----------------------
arch/ia64/mm/discontig.c | 134 ++++++-----------------------------------------
4 files changed, 33 insertions(+), 188 deletions(-)
--
2.7.4
next reply other threads:[~2018-07-23 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 5:56 Mike Rapoport [this message]
2018-07-23 5:56 ` [PATCH 1/4] ia64: contig/paging_init: reduce code duplication Mike Rapoport
2018-07-23 5:56 ` [PATCH 2/4] ia64: remove unused num_dma_physpages member from 'struct early_node_data' Mike Rapoport
2018-07-23 5:56 ` [PATCH 3/4] ia64: use mem_data to detect nodes' minimal and maximal PFNs Mike Rapoport
2018-07-23 5:56 ` [PATCH 4/4] ia64: switch to NO_BOOTMEM Mike Rapoport
2018-07-23 21:00 ` [PATCH 0/4] " Luck, Tony
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=1532325418-22617-1-git-send-email-rppt@linux.vnet.ibm.com \
--to=rppt@linux.vnet.ibm.com \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox