From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Kevin Lourenco <klourencodev@gmail.com>
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:46:06 +0100 [thread overview]
Message-ID: <f13ef321-3987-48b5-99f7-5e0a12e2ad29@kernel.org> (raw)
In-Reply-To: <CAFveykPV1ZFWWgu+HK090njGoMDqhH5SAd9EmG-+VO9a4vLg4A@mail.gmail.com>
On 12/18/25 13:21, Kevin Lourenco wrote:
> 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.
Hi Kevin,
then please send all of them in a single series, combining them in
patches where reasonable.
For example, the feedback I gave you should be applied to all patches
(e.g., subject prefix, patch description).
Imagine doing that as a reviewer to 20 individual patches from 20
individual contributors :)
--
Cheers
David
prev parent reply other threads:[~2025-12-18 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 11:20 [PATCH] Correct minor spelling mistake in huge_memory.c klourencodev
2025-12-18 11:54 ` David Hildenbrand (Red Hat)
2025-12-18 12:21 ` Kevin Lourenco
2025-12-18 12:46 ` David Hildenbrand (Red Hat) [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=f13ef321-3987-48b5-99f7-5e0a12e2ad29@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=klourencodev@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.