From: Mike Rapoport <rppt@kernel.org>
To: Prabhav Kumar Vaish <pvkumar5749404@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Fix typos in comments in mm_init.c
Date: Mon, 21 Apr 2025 19:42:06 +0300 [thread overview]
Message-ID: <aAZ1XnTO4xUQf9ow@kernel.org> (raw)
In-Reply-To: <20250420140440.18817-1-pvkumar5749404@gmail.com>
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@gmail.com>
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.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.
prev parent reply other threads:[~2025-04-21 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 14:04 Prabhav Kumar Vaish
2025-04-21 16:42 ` Mike Rapoport [this message]
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=aAZ1XnTO4xUQf9ow@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pvkumar5749404@gmail.com \
/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