linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] mm/memblock: Correct doc for function
@ 2019-11-13  5:18 Shiyang Ruan
  2019-11-13 10:33 ` Mike Rapoport
  0 siblings, 1 reply; 2+ messages in thread
From: Shiyang Ruan @ 2019-11-13  5:18 UTC (permalink / raw)
  To: linux-mm, linux-kernel; +Cc: rppt, akpm, Cao jin

From: Cao jin <caoj.fnst@cn.fujitsu.com>

Change "max_addr" to "end" for less confusion
in memblock_alloc_range_nid comments.

Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
---
 mm/memblock.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Suppose this still goes to Andrew's -mm.

diff --git a/mm/memblock.c b/mm/memblock.c
index ceb6761f526d..203ed317551b 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -1321,7 +1321,7 @@ __next_mem_pfn_range_in_zone(u64 *idx, struct zone *zone,
  * @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
-- 
2.21.0




^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] mm/memblock: Correct doc for function
  2019-11-13  5:18 [PATCH] mm/memblock: Correct doc for function Shiyang Ruan
@ 2019-11-13 10:33 ` Mike Rapoport
  0 siblings, 0 replies; 2+ messages in thread
From: Mike Rapoport @ 2019-11-13 10:33 UTC (permalink / raw)
  To: Shiyang Ruan; +Cc: linux-mm, linux-kernel, akpm, Cao jin

On Wed, Nov 13, 2019 at 01:18:22PM +0800, Shiyang Ruan wrote:
> From: Cao jin <caoj.fnst@cn.fujitsu.com>
> 
> Change "max_addr" to "end" for less confusion
> in memblock_alloc_range_nid comments.
> 
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>

Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>

> ---
>  mm/memblock.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Suppose this still goes to Andrew's -mm.
> 
> diff --git a/mm/memblock.c b/mm/memblock.c
> index ceb6761f526d..203ed317551b 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -1321,7 +1321,7 @@ __next_mem_pfn_range_in_zone(u64 *idx, struct zone *zone,
>   * @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
> -- 
> 2.21.0
> 
> 
> 

-- 
Sincerely yours,
Mike.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-11-13 10:34 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-13  5:18 [PATCH] mm/memblock: Correct doc for function Shiyang Ruan
2019-11-13 10:33 ` Mike Rapoport

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).