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 2/2] fork: change "a mm_struct" to "an mm_struct" in comment
Date: Wed, 3 Sep 2025 20:23:26 -1000 [thread overview]
Message-ID: <1c468cd846ba6839fea08df36d8d6e9718625661.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>
---
kernel/fork.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/fork.c b/kernel/fork.c
index af673856499dcaa35e..9a783cd46d097a2d68 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -1397,18 +1397,18 @@ static int wait_for_vfork_done(struct task_struct *child,
put_task_struct(child);
return killed;
}
/* Please note the differences between mmput and mm_release.
- * mmput is called whenever we stop holding onto a mm_struct,
+ * mmput is called whenever we stop holding onto an mm_struct,
* error success whatever.
*
- * mm_release is called after a mm_struct has been removed
+ * mm_release is called after an mm_struct has been removed
* from the current process.
*
* This difference is important for error handling, when we
- * only half set up a mm_struct for a new process and need to restore
+ * only half set up an mm_struct for a new process and need to restore
* the old one. Because we mmput the new mm_struct before
* restoring the old one. . .
* Eric Biederman 10 January 1998
*/
static void mm_release(struct task_struct *tsk, struct mm_struct *mm)
--
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 ` [PATCH 1/2] Hexagon: " Joey Pabalinas
2025-09-04 6:23 ` Joey Pabalinas [this message]
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=1c468cd846ba6839fea08df36d8d6e9718625661.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