linux-kernel - [PATCH] mm/memblock: Correct doc for function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191113051822.3296-1-ruansy.fnst@cn.fujitsu.com>
Date:   Wed, 13 Nov 2019 13:18:22 +0800
From:   Shiyang Ruan <ruansy.fnst@...fujitsu.com>
To:     <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
CC:     <rppt@...ux.ibm.com>, <akpm@...ux-foundation.org>,
        Cao jin <caoj.fnst@...fujitsu.com>
Subject: [PATCH] mm/memblock: Correct doc for function

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

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

Signed-off-by: Cao jin <caoj.fnst@...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