[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190911030856.18010-1-caoj.fnst@cn.fujitsu.com>
Date: Wed, 11 Sep 2019 11:08:56 +0800
From: Cao jin <caoj.fnst@...fujitsu.com>
To: <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
CC: <rppt@...ux.ibm.com>
Subject: [PATCH] mm/memblock: fix typo in memblock doc
elaboarte -> elaborate
architecure -> architecture
compltes -> completes
Signed-off-by: Cao jin <caoj.fnst@...fujitsu.com>
---
mm/memblock.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/mm/memblock.c b/mm/memblock.c
index 7d4f61ae666a..0d0f92003d18 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -83,16 +83,16 @@
* Note, that both API variants use implict assumptions about allowed
* memory ranges and the fallback methods. Consult the documentation
* of :c:func:`memblock_alloc_internal` and
- * :c:func:`memblock_alloc_range_nid` functions for more elaboarte
+ * :c:func:`memblock_alloc_range_nid` functions for more elaborate
* description.
*
* As the system boot progresses, the architecture specific
* :c:func:`mem_init` function frees all the memory to the buddy page
* allocator.
*
- * Unless an architecure enables %CONFIG_ARCH_KEEP_MEMBLOCK, the
+ * Unless an architecture enables %CONFIG_ARCH_KEEP_MEMBLOCK, the
* memblock data structures will be discarded after the system
- * initialization compltes.
+ * initialization completes.
*/
#ifndef CONFIG_NEED_MULTIPLE_NODES
--
2.21.0
Powered by blists - more mailing lists