[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231006112636.97128-1-amos@bearcove.net>
Date: Fri, 6 Oct 2023 13:26:36 +0200
From: Amos Wenger <amos@...rcove.net>
To: amos@...rcove.net
Cc: David Hildenbrand <david@...hat.com>,
Oscar Salvador <osalvador@...e.de>,
Jonathan Corbet <corbet@....net>,
linux-mm@...ck.org (open list:MEMORY HOT(UN)PLUG),
linux-doc@...r.kernel.org (open list:DOCUMENTATION),
linux-kernel@...r.kernel.org (open list)
Subject: [PATCH] mm/memory-hotplug: fix typo in documentation
I'm 90% sure memory hotunplugging doesn't involve a "fist" phase
Signed-off-by: Amos Wenger <amos@...rcove.net>
---
Documentation/admin-guide/mm/memory-hotplug.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/mm/memory-hotplug.rst b/Documentation/admin-guide/mm/memory-hotplug.rst
index cfe034cf1e87..fbf2c22f890d 100644
--- a/Documentation/admin-guide/mm/memory-hotplug.rst
+++ b/Documentation/admin-guide/mm/memory-hotplug.rst
@@ -75,7 +75,7 @@ Memory hotunplug consists of two phases:
(1) Offlining memory blocks
(2) Removing the memory from Linux
-In the fist phase, memory is "hidden" from the page allocator again, for
+In the first phase, memory is "hidden" from the page allocator again, for
example, by migrating busy memory to other memory locations and removing all
relevant free pages from the page allocator After this phase, the memory is no
longer visible in memory statistics of the system.
--
2.39.2
Powered by blists - more mailing lists