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] [day] [month] [year] [list]
Message-ID: <aAZ1XnTO4xUQf9ow@kernel.org>
Date: Mon, 21 Apr 2025 19:42:06 +0300
From: Mike Rapoport <rppt@...nel.org>
To: Prabhav Kumar Vaish <pvkumar5749404@...il.com>
Cc: akpm@...ux-foundation.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: Fix typos in comments in mm_init.c

On Sun, Apr 20, 2025 at 07:34:40PM +0530, Prabhav Kumar Vaish wrote:
> Corrected minor typos in comments:
> 	- 'contigious' -> 'contiguous'
> 	- 'hierarcy' -> 'hierarchy'
> 
> This is a non-functional change in comment text only.
> 
> Signed-off-by: Prabhav Kumar Vaish <pvkumar5749404@...il.com>

Reviewed-by: Mike Rapoport (Microsoft) <rppt@...nel.org>

> ---
>  mm/mm_init.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/mm_init.c b/mm/mm_init.c
> index 9659689b8ace..7f3361fd5392 100644
> --- a/mm/mm_init.c
> +++ b/mm/mm_init.c
> @@ -828,7 +828,7 @@ overlap_memmap_init(unsigned long zone, unsigned long *pfn)
>   * - physical memory bank size is not necessarily the exact multiple of the
>   *   arbitrary section size
>   * - early reserved memory may not be listed in memblock.memory
> - * - non-memory regions covered by the contigious flatmem mapping
> + * - non-memory regions covered by the contiguous flatmem mapping
>   * - memory layouts defined with memmap= kernel parameter may not align
>   *   nicely with memmap sections
>   *
> @@ -1908,7 +1908,7 @@ void __init free_area_init(unsigned long *max_zone_pfn)
>  		free_area_init_node(nid);
>  
>  		/*
> -		 * No sysfs hierarcy will be created via register_one_node()
> +		 * No sysfs hierarchy will be created via register_one_node()
>  		 *for memory-less node because here it's not marked as N_MEMORY
>  		 *and won't be set online later. The benefit is userspace
>  		 *program won't be confused by sysfs files/directories of
> -- 
> 2.34.1
> 

-- 
Sincerely yours,
Mike.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ