From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Oleg Nesterov <oleg@redhat.com>,
x86@kernel.org
Subject: [PATCH] signal: Correct spelling typos in ptrace_stop().
Date: Wed, 20 Sep 2023 09:47:52 +0200 [thread overview]
Message-ID: <20230920074752.G21mcqOI@linutronix.de> (raw)
In-Reply-To: <ZQqXvPhesRmAtjvR@gmail.com>
Ingo spotted typos in the recently added comment and suggested
corrections.
Use 'On' instead of 'One' and remove one superfluous 'the' in a
sentence.
Suggested-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
kernel/signal.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index f2a5578326ade..384b77ad1bc15 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -2330,7 +2330,7 @@ static int ptrace_stop(int exit_code, int why, unsigned long message,
/*
* The previous do_notify_parent_cldstop() invocation woke ptracer.
- * One a PREEMPTION kernel this can result in preemption requirement
+ * On a PREEMPTION kernel this can result in preemption requirement
* which will be fulfilled after read_unlock() and the ptracer will be
* put on the CPU.
* The ptracer is in wait_task_inactive(, __TASK_TRACED) waiting for
@@ -2343,7 +2343,7 @@ static int ptrace_stop(int exit_code, int why, unsigned long message,
* view but extends the runtime by one HZ tick time due to the
* ptracer's sleep. The preempt-disable section ensures that there
* will be no preemption between unlock and schedule() and so
- * improving the performance since the ptracer will observe that
+ * improving performance since the ptracer will observe that
* the tracee is scheduled out once it gets on the CPU.
*
* On PREEMPT_RT locking tasklist_lock does not disable preemption.
--
2.40.1
next prev parent reply other threads:[~2023-09-20 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 10:09 [PATCH REPOST v3 0/2] signal: Avoid preempt_disable() in ptrace_stop() on PREEMPT_RT Sebastian Andrzej Siewior
2023-08-03 10:09 ` [PATCH 1/2] signal: Add proper comment about the preempt-disable in ptrace_stop() Sebastian Andrzej Siewior
2023-09-19 20:16 ` [tip: core/core] signal: Add a proper comment about preempt_disable() " tip-bot2 for Sebastian Andrzej Siewior
2023-09-20 6:57 ` Ingo Molnar
2023-09-20 7:47 ` Sebastian Andrzej Siewior [this message]
2023-08-03 10:09 ` [PATCH 2/2] signal: Don't disable preemption in ptrace_stop() on PREEMPT_RT Sebastian Andrzej Siewior
2023-09-19 20:16 ` [tip: core/core] " tip-bot2 for Sebastian Andrzej Siewior
2023-08-17 13:46 ` [PATCH REPOST v3 0/2] signal: Avoid preempt_disable() " Sebastian Andrzej Siewior
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=20230920074752.G21mcqOI@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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