From: David Hildenbrand <david@redhat.com>
To: Amos Wenger <amos@bearcove.net>
Cc: Oscar Salvador <osalvador@suse.de>,
Jonathan Corbet <corbet@lwn.net>,
"open list:MEMORY HOT(UN)PLUG" <linux-mm@kvack.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/memory-hotplug: fix typo in documentation
Date: Fri, 6 Oct 2023 13:46:49 +0200 [thread overview]
Message-ID: <6fa290a6-0e1b-856e-cda0-2e99de6de53f@redhat.com> (raw)
In-Reply-To: <20231006112636.97128-1-amos@bearcove.net>
On 06.10.23 13:26, Amos Wenger wrote:
> I'm 90% sure memory hotunplugging doesn't involve a "fist" phase
:D Thanks!
Reviewed-by: David Hildenbrand <david@redhat.com>
>
> 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.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-10-06 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 11:26 Amos Wenger
2023-10-06 11:46 ` David Hildenbrand [this message]
2023-10-10 19:12 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6fa290a6-0e1b-856e-cda0-2e99de6de53f@redhat.com \
--to=david@redhat.com \
--cc=amos@bearcove.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox