The patch titled
Subject: mm/memblock: correct doc for function
has been removed from the -mm tree. Its filename was
mm-memblock-correct-doc-for-function.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Cao jin <caoj.fnst@xxxxxxxxxxxxxx>
Subject: mm/memblock: correct doc for function
Change "max_addr" to "end" for less confusion in memblock_alloc_range_nid
comments.
Link: http://lkml.kernel.org/r/20191113051822.3296-1-ruansy.fnst@xxxxxxxxxxxxxx
Signed-off-by: Cao jin <caoj.fnst@xxxxxxxxxxxxxx>
Signed-off-by: Shiyang Ruan <ruansy.fnst@xxxxxxxxxxxxxx>
Reviewed-by: Mike Rapoport <rppt@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/memblock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/memblock.c~mm-memblock-correct-doc-for-function
+++ a/mm/memblock.c
@@ -1321,7 +1321,7 @@ __next_mem_pfn_range_in_zone(u64 *idx, s
* @nid: nid of the free area to find, %NUMA_NO_NODE for any node
*
* The allocation is performed from memory region limited by
- * memblock.current_limit if @max_addr == %MEMBLOCK_ALLOC_ACCESSIBLE.
+ * memblock.current_limit if @end == %MEMBLOCK_ALLOC_ACCESSIBLE.
*
* If the specified node can not hold the requested memory the
* allocation falls back to any node in the system
_
Patches currently in -mm which might be from caoj.fnst@xxxxxxxxxxxxxx are
