linux-kernel - Re: [PATCH] mm/memory-hotplug: fix typo in documentation

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6fa290a6-0e1b-856e-cda0-2e99de6de53f@redhat.com>
Date:   Fri, 6 Oct 2023 13:46:49 +0200
From:   David Hildenbrand <david@...hat.com>
To:     Amos Wenger <amos@...rcove.net>
Cc:     Oscar Salvador <osalvador@...e.de>,
        Jonathan Corbet <corbet@....net>,
        "open list:MEMORY HOT(UN)PLUG" <linux-mm@...ck.org>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/memory-hotplug: fix typo in documentation

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@...hat.com>

> 
> 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.

-- 
Cheers,

David / dhildenb