From: Joey Pabalinas <joeypabalinas@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-hexagon@vger.kernel.org, linux-mm@kvack.org,
Brian Cain <bcain@kernel.org>, Kees Cook <kees@kernel.org>,
Joey Pabalinas <joeypabalinas@gmail.com>
Subject: [PATCH 1/2] Hexagon: change "a mm_struct" to "an mm_struct" in comment
Date: Wed, 3 Sep 2025 20:23:25 -1000 [thread overview]
Message-ID: <4c3812e5903e4e91587eff3c37b7aee4b35ddf20.1756966290.git.joeypabalinas@gmail.com> (raw)
In-Reply-To: <cover.1756966290.git.joeypabalinas@gmail.com>
The correct english is "an mm_struct" which is used everywhere else
in the kernel.
Signed-off-by: Joey Pabalinas <joeypabalinas@gmail.com>
---
arch/hexagon/include/asm/mmu.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/hexagon/include/asm/mmu.h b/arch/hexagon/include/asm/mmu.h
index dfa46660d695bb65b4..ce784218dc67c92a94 100644
--- a/arch/hexagon/include/asm/mmu.h
+++ b/arch/hexagon/include/asm/mmu.h
@@ -7,11 +7,11 @@
#define _ASM_MMU_H
#include <asm/vdso.h>
/*
- * Architecture-specific state for a mm_struct.
+ * Architecture-specific state for an mm_struct.
* For the Hexagon Virtual Machine, it can be a copy
* of the pointer to the page table base.
*/
struct mm_context {
unsigned long long generation;
--
Cheers,
Joey Pabalinas
next prev parent reply other threads:[~2025-09-04 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 6:23 [PATCH 0/2] " Joey Pabalinas
2025-09-04 6:23 ` Joey Pabalinas [this message]
2025-09-04 6:23 ` [PATCH 2/2] fork: " Joey Pabalinas
2025-09-04 10:46 ` [PATCH 0/2] " Lorenzo Stoakes
2025-09-04 10:52 ` 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=4c3812e5903e4e91587eff3c37b7aee4b35ddf20.1756966290.git.joeypabalinas@gmail.com \
--to=joeypabalinas@gmail.com \
--cc=bcain@kernel.org \
--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