From: Kevin Lourenco <klourencodev@gmail.com>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
lorenzo.stoakes@oracle.com, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
ryan.roberts@arm.com
Subject: Re: [PATCH] Correct minor spelling mistake in huge_memory.c.
Date: Thu, 18 Dec 2025 13:21:07 +0100 [thread overview]
Message-ID: <CAFveykPV1ZFWWgu+HK090njGoMDqhH5SAd9EmG-+VO9a4vLg4A@mail.gmail.com> (raw)
In-Reply-To: <0544a9e4-bfef-4af8-9f68-a5aade840adf@kernel.org>
Hi David,
I have found no other spelling issues. I also did a deeper review of
the mm/ directory in general and identified more than 20 evident typos
across various files.
I was considering cleaning all of mm/ in one go to provide a more
thorough and consistent update. However, if you feel that doing so
would not add significant value and would only consume reviewer / my
time, I completely understand and can refrain from submitting them.
Alternatively, I could create a single patch that addresses all the
typos at once in mm/.
Please let me know your preference.
Best regards,
Kevin
Le jeu. 18 déc. 2025 à 12:54, David Hildenbrand (Red Hat)
<david@kernel.org> a écrit :
>
> On 12/18/25 12:20, klourencodev@gmail.com wrote:
> > From: Kevin Lourenco <klourencodev@gmail.com>
> >
> > No functional changes.
>
> Subject: "mm/huge_memory: correct minor spelling mistake"
>
> Then a simple "Let's correct progated -> propagated in a comment."
>
> You can drop the "no functional change" part as you only modify a comment.
>
> >
> > Signed-off-by: Kevin Lourenco <klourencodev@gmail.com>
> > ---
> > mm/huge_memory.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> > index 40cf59301c21..5efd2cf4f073 100644
> > --- a/mm/huge_memory.c
> > +++ b/mm/huge_memory.c
> > @@ -3220,7 +3220,7 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd,
> > swp_entry = make_readable_device_private_entry(
> > page_to_pfn(page + i));
> > /*
> > - * Young and dirty bits are not progated via swp_entry
> > + * Young and dirty bits are not propagated via swp_entry
> > */
> > entry = swp_entry_to_pte(swp_entry);
> > if (soft_dirty)
>
> Are there any other spelling issues in that file so we can avoid more of
> these patches that don't add a lot of value and only consume reviewer time?
>
> --
> Cheers
>
> David
next prev parent reply other threads:[~2025-12-18 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 11:20 klourencodev
2025-12-18 11:54 ` David Hildenbrand (Red Hat)
2025-12-18 12:21 ` Kevin Lourenco [this message]
2025-12-18 12:46 ` David Hildenbrand (Red Hat)
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=CAFveykPV1ZFWWgu+HK090njGoMDqhH5SAd9EmG-+VO9a4vLg4A@mail.gmail.com \
--to=klourencodev@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ryan.roberts@arm.com \
--cc=ziy@nvidia.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