[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1c468cd846ba6839fea08df36d8d6e9718625661.1756966290.git.joeypabalinas@gmail.com>
Date: Wed, 3 Sep 2025 20:23:26 -1000
From: Joey Pabalinas <joeypabalinas@...il.com>
To: linux-kernel@...r.kernel.org
Cc: linux-hexagon@...r.kernel.org,
linux-mm@...ck.org,
Brian Cain <bcain@...nel.org>,
Kees Cook <kees@...nel.org>,
Joey Pabalinas <joeypabalinas@...il.com>
Subject: [PATCH 2/2] fork: change "a mm_struct" to "an mm_struct" in comment
The correct english is "an mm_struct" which is used everywhere else
in the kernel.
Signed-off-by: Joey Pabalinas <joeypabalinas@...il.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
Powered by blists - more mailing lists