linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] mm/memory-hotplug: fix typo in documentation
@ 2023-10-06 11:26 Amos Wenger
  2023-10-06 11:46 ` David Hildenbrand
  2023-10-10 19:12 ` Jonathan Corbet
  0 siblings, 2 replies; 3+ messages in thread
From: Amos Wenger @ 2023-10-06 11:26 UTC (permalink / raw)
  To: amos
  Cc: David Hildenbrand, Oscar Salvador, Jonathan Corbet,
	open list:MEMORY HOT(UN)PLUG, open list:DOCUMENTATION, open list

I'm 90% sure memory hotunplugging doesn't involve a "fist" phase

Signed-off-by: Amos Wenger <amos@bearcove.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



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

end of thread, other threads:[~2023-10-10 19:12 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-06 11:26 [PATCH] mm/memory-hotplug: fix typo in documentation Amos Wenger
2023-10-06 11:46 ` David Hildenbrand
2023-10-10 19:12 ` Jonathan Corbet

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox