mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK
Status from this message: [merged] mm-memory_hotplug-handle-memblocks-only-with-config_arch_keep_memblock.patch removed from -mm tree
Get series with b4
b4 am [email protected]Versions newest first
Changes in v1 from the cover letter
- Added ACKs
- Rephrased subject/description of patch #1
- Use IS_ENABLED() instead of ifdefs in patch #2
Patches in v1 All 2 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm/memory_hotplug: set node_start_pfn of hotadded pgdat to 0mm/ | +6 | 0 replies | Applied |
| 2/2 | mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCKmm/ mm/ | +13 | 0 replies | Applied |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Pankaj Gupta | Mike Rapoport | Michal Hocko |
|---|---|---|---|
| 1/2 | A-b | ||
| 2/2 | A-b | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.
Cover letter [PATCH v1 0/2] mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK
While working on some other cleanups I stumbled over the creation/removal of memblocks in hotplug code and wondered why we still need that. Turns out, we only need that handling with CONFIG_ARCH_KEEP_MEMBLOCK.
Gave it a quick test on x86-64.
RFC -> v1:
- Added ACKs
- Rephrased subject/description of patch #1
- Use IS_ENABLED() instead of ifdefs in patch #2
David Hildenbrand (2):
mm/memory_hotplug: set node_start_pfn of hotadded pgdat to 0 mm/memory_hotplug: handle memblocks only with
CONFIG_ARCH_KEEP_MEMBLOCK
mm/Kconfig | 3 +++ mm/memory_hotplug.c | 35 ++++++++++++++++------------------- 2 files changed, 19 insertions(+), 19 deletions(-)
Signature · 1 line
2.25.3