From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Ye Liu <ye.liu@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Ye Liu <liuye@kylinos.cn>, Vlastimil Babka <vbabka@suse.cz>,
Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Fix typos in VMA comments
Date: Thu, 14 Aug 2025 08:43:03 +0100 [thread overview]
Message-ID: <5108b2fd-c6a5-44c5-93f6-6ff9fc2ae783@lucifer.local> (raw)
In-Reply-To: <20250814073800.13617-1-ye.liu@linux.dev>
On Thu, Aug 14, 2025 at 03:37:59PM +0800, Ye Liu wrote:
> From: Ye Liu <liuye@kylinos.cn>
>
> Fixed the following typos in VMA-related files:
> 1. "operationr" -> "operation" in mm/vma.h
> 2. "initialisaing" -> "initializing" in mm/vma_init.c
>
> Signed-off-by: Ye Liu <liuye@kylinos.cn>
Seems I am the typo king :)
LGTM, so:
Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
> mm/vma.h | 2 +-
> mm/vma_init.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/vma.h b/mm/vma.h
> index b123a9cdedb0..bcdc261c5b15 100644
> --- a/mm/vma.h
> +++ b/mm/vma.h
> @@ -145,7 +145,7 @@ struct vma_merge_struct {
> */
> bool __remove_middle :1;
> /*
> - * Internal flag used during the merge operationr to indicate we will
> + * Internal flag used during the merge operation to indicate we will
> * remove vmg->next.
> */
> bool __remove_next :1;
> diff --git a/mm/vma_init.c b/mm/vma_init.c
> index 8e53c7943561..d847c6557261 100644
> --- a/mm/vma_init.c
> +++ b/mm/vma_init.c
> @@ -1,7 +1,7 @@
> // SPDX-License-Identifier: GPL-2.0-or-later
>
> /*
> - * Functions for initialisaing, allocating, freeing and duplicating VMAs. Shared
> + * Functions for initializing, allocating, freeing and duplicating VMAs. Shared
I typically use the British 'initialising' spelling of the word (when not
typo'ing it :P) but I don't mind using the American English form either as
that's almost a standard in the kernel in practice.
> * between CONFIG_MMU and non-CONFIG_MMU kernel configurations.
> */
>
> --
> 2.43.0
>
prev parent reply other threads:[~2025-08-14 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 7:37 Ye Liu
2025-08-14 7:43 ` Lorenzo Stoakes [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=5108b2fd-c6a5-44c5-93f6-6ff9fc2ae783@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=pfalcato@suse.de \
--cc=vbabka@suse.cz \
--cc=ye.liu@linux.dev \
/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