From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Joey Pabalinas <joeypabalinas@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-mm@kvack.org, Brian Cain <bcain@kernel.org>,
Kees Cook <kees@kernel.org>
Subject: Re: [PATCH 0/2] change "a mm_struct" to "an mm_struct" in comment
Date: Thu, 4 Sep 2025 11:46:52 +0100 [thread overview]
Message-ID: <247f1fb3-6966-4789-8f26-7d4126318c5f@lucifer.local> (raw)
In-Reply-To: <cover.1756966290.git.joeypabalinas@gmail.com>
On Wed, Sep 03, 2025 at 08:23:24PM -1000, Joey Pabalinas wrote:
> The correct english is "an mm_struct" which is used everywhere else
> in the kernel.
Hi Joey, this doesn't really warrant a patch, it's just not important and there
isn't great RoI on the churcn here. It is also very silly to make this two
patches, it should only be one.
Also please do run scripts/get_maintainers.pl when you're doing this, Kees is on
the list but he is joined by many esteemed kernel colleagues ;))
Ingo Molnar <mingo@redhat.com> (maintainer:SCHEDULER)
Peter Zijlstra <peterz@infradead.org> (maintainer:SCHEDULER)
Juri Lelli <juri.lelli@redhat.com> (maintainer:SCHEDULER)
Vincent Guittot <vincent.guittot@linaro.org> (maintainer:SCHEDULER)
Dietmar Eggemann <dietmar.eggemann@arm.com> (reviewer:SCHEDULER)
Steven Rostedt <rostedt@goodmis.org> (reviewer:SCHEDULER)
Ben Segall <bsegall@google.com> (reviewer:SCHEDULER)
Mel Gorman <mgorman@suse.de> (reviewer:SCHEDULER)
Valentin Schneider <vschneid@redhat.com> (reviewer:SCHEDULER)
Kees Cook <kees@kernel.org> (maintainer:EXEC & BINFMT API, ELF)
Andrew Morton <akpm@linux-foundation.org> (maintainer:MEMORY MANAGEMENT - CORE)
David Hildenbrand <david@redhat.com> (maintainer:MEMORY MANAGEMENT - CORE)
Lorenzo Stoakes <lorenzo.stoakes@oracle.com> (reviewer:MEMORY MANAGEMENT - CORE)
"Liam R. Howlett" <Liam.Howlett@oracle.com> (reviewer:MEMORY MANAGEMENT - CORE)
Vlastimil Babka <vbabka@suse.cz> (reviewer:MEMORY MANAGEMENT - CORE)
Mike Rapoport <rppt@kernel.org> (reviewer:MEMORY MANAGEMENT - CORE)
Suren Baghdasaryan <surenb@google.com> (reviewer:MEMORY MANAGEMENT - CORE)
Michal Hocko <mhocko@suse.com> (reviewer:MEMORY MANAGEMENT - CORE)
Brian Cain <bcain@kernel.org> (maintainer:QUALCOMM HEXAGON ARCHITECTURE)
linux-kernel@vger.kernel.org (open list:SCHEDULER)
linux-mm@kvack.org (open list:EXEC & BINFMT API, ELF)
linux-hexagon@vger.kernel.org (open list:QUALCOMM HEXAGON ARCHITECTURE)
EXEC & BINFMT API, ELF status: Supported
QUALCOMM HEXAGON ARCHITECTURE status: Supported
>
> Joey Pabalinas (2):
> Hexagon: change "a mm_struct" to "an mm_struct" in comment
> fork: change "a mm_struct" to "an mm_struct" in comment
>
> arch/hexagon/include/asm/mmu.h | 2 +-
> kernel/fork.c | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> --
> Cheers,
> Joey Pabalinas
>
>
>
So yeah I don't think we should take this, sorry! :(
Cheers, Lorenzo
next prev parent reply other threads:[~2025-09-04 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 6:23 Joey Pabalinas
2025-09-04 6:23 ` [PATCH 1/2] Hexagon: " Joey Pabalinas
2025-09-04 6:23 ` [PATCH 2/2] fork: " Joey Pabalinas
2025-09-04 10:46 ` Lorenzo Stoakes [this message]
2025-09-04 10:52 ` [PATCH 0/2] " Lorenzo Stoakes
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=247f1fb3-6966-4789-8f26-7d4126318c5f@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=bcain@kernel.org \
--cc=joeypabalinas@gmail.com \
--cc=kees@kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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