* [to-be-updated] mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix.patch removed from -mm tree
@ 2021-03-19 15:45 akpm
0 siblings, 0 replies; 2+ messages in thread
From: akpm @ 2021-03-19 15:45 UTC (permalink / raw)
To: akpm, anshuman.khandual, david, mhocko, mm-commits, osalvador,
pasha.tatashin, vbabka
The patch titled
Subject: mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix
has been removed from the -mm tree. Its filename was
mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix
reflow comment
Cc: Oscar Salvador <osalvador@suse.de>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: Michal Hocko <mhocko@kernel.org>
Cc: Pavel Tatashin <pasha.tatashin@soleen.com>
Cc: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/mmzone.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- a/include/linux/mmzone.h~mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix
+++ a/include/linux/mmzone.h
@@ -436,9 +436,9 @@ enum zone_type {
* situations where ZERO_PAGE(0) which is allocated differently
* on different platforms may end up in a movable zone. ZERO_PAGE(0)
* cannot be migrated.
- * 7. Memory-hotplug: when using memmap_on_memory and onlining the memory
- * to the MOVABLE zone, the vmemmap pages are also placed in such
- * zone. Such pages cannot be really moved around as they are
+ * 7. Memory-hotplug: when using memmap_on_memory and onlining the
+ * memory to the MOVABLE zone, the vmemmap pages are also placed in
+ * such zone. Such pages cannot be really moved around as they are
* self-stored in the range, but they are treated as movable when
* the range they describe is about to be offlined.
*
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm.patch
mm-memcontrol-switch-to-rstat-fix.patch
kasan-remove-redundant-config-option-fix.patch
linux-next-rejects.patch
kernel-forkc-export-kernel_thread-to-modules.patch
^ permalink raw reply [flat|nested] 2+ messages in thread
* [to-be-updated] mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix.patch removed from -mm tree
@ 2021-04-16 18:12 akpm
0 siblings, 0 replies; 2+ messages in thread
From: akpm @ 2021-04-16 18:12 UTC (permalink / raw)
To: mm-commits, vbabka, pasha.tatashin, osalvador, mhocko, david,
anshuman.khandual, akpm
The patch titled
Subject: mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix
has been removed from the -mm tree. Its filename was
mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix
typo & code cleanup, per David
Cc: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: Michal Hocko <mhocko@kernel.org>
Cc: Oscar Salvador <osalvador@suse.de>
Cc: Pavel Tatashin <pasha.tatashin@soleen.com>
Cc: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memory_hotplug.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/mm/memory_hotplug.c~mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix
+++ a/mm/memory_hotplug.c
@@ -1097,7 +1097,7 @@ bool mhp_supports_memmap_on_memory(unsig
* Besides having arch support and the feature enabled at runtime, we
* need a few more assumptions to hold true:
*
- * a) We span a single memory block: memory onlining/offlinin;g happens
+ * a) We span a single memory block: memory onlining/offlining happens
* in memory block granularity. We don't want the vmemmap of online
* memory blocks to reside on offline memory blocks. In the future,
* we might want to support variable-sized memory blocks to make the
@@ -1123,7 +1123,7 @@ bool mhp_supports_memmap_on_memory(unsig
IS_ENABLED(CONFIG_MHP_MEMMAP_ON_MEMORY) &&
size == memory_block_size_bytes() &&
IS_ALIGNED(vmemmap_size, PMD_SIZE) &&
- IS_ALIGNED(remaining_size, (pageblock_nr_pages << PAGE_SHIFT));
+ IS_ALIGNED(remaining_size, pageblock_nr_pages << PAGE_SHIFT);
}
/*
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
scripts-a-new-script-for-checking-duplicate-struct-declaration-fix.patch
mm.patch
mm-memcontrol-switch-to-rstat-fix.patch
mm-vmalloc-remove-unmap_kernel_range-fix-fix.patch
mm-page_alloc-add-an-array-based-interface-to-the-bulk-page-allocator-fix.patch
mm-vmscan-add-shrinker_info_protected-helper-fix.patch
mm-drop-redundant-arch_enable__migration-fix.patch
mm-drop-redundant-arch_enable__migration-fix-fix.patch
linux-next-rejects.patch
linux-next-git-rejects.patch
kernel-forkc-export-kernel_thread-to-modules.patch
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-04-16 18:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-19 15:45 [to-be-updated] mmmemory_hotplug-allocate-memmap-from-the-added-memory-range-fix.patch removed from -mm tree akpm
2021-04-16 18:12 akpm
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.