mm-sparse-use-memblock_alloc_accessible-enum-instead-of-0.patch removed from -mm tree
The quilt patch titled
Subject: mm/sparse: use MEMBLOCK_ALLOC_ACCESSIBLE enum instead of 0
has been removed from the -mm tree. Its filename was
mm-sparse-use-memblock_alloc_accessible-enum-instead-of-0.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Leesoo Ahn <[email protected]>
Subject: mm/sparse: use MEMBLOCK_ALLOC_ACCESSIBLE enum instead of 0
Date: Tue, 11 Jun 2024 00:15:28 +0900
Setting 'limit' variable to 0 might seem like it means "no limit". But in the memblock API, 0 actually means the 'MEMBLOCK_ALLOC_ACCESSIBLE' enum, which limits the physical address range end based on 'memblock.current_limit'. This could be confusing.
Use the enum instead of 0 to make it clear.
---
mm/sparse.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/sparse.c renamed from mm/sparse.c~mm-sparse-use-memblock_alloc_accessible-enum-instead-of-0 +1 -1
@@ -351,7 +351,7 @@ sparse_early_usemaps_alloc_pgdat_section again: usage =memblock_alloc_try_nid (size,SMP_CACHE_BYTES , goal, limit, nid);if (!usage && limit) { - limit =0 ; + limit =MEMBLOCK_ALLOC_ACCESSIBLE ; goto again; }return usage;
_
Patches currently in -mm which might be from [email protected] are