* [patch 121/158] mm/memblock: correct doc for function
@ 2019-12-01 1:56 akpm
0 siblings, 0 replies; only message in thread
From: akpm @ 2019-12-01 1:56 UTC (permalink / raw)
To: akpm, caoj.fnst, linux-mm, mm-commits, rppt, ruansy.fnst, torvalds
From: Cao jin <caoj.fnst@cn.fujitsu.com>
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@cn.fujitsu.com
Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
Signed-off-by: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>
Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
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
_
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-12-01 1:56 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-01 1:56 [patch 121/158] mm/memblock: correct doc for function akpm
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox