From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: tsbogend@alpha.franken.de, peterz@infradead.org,
frederic@kernel.org, mingo@kernel.org, peterx@redhat.com,
afzal.mohd.ma@gmail.com, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: rdunlap@infradead.org, Bhaskar Chowdhury <unixbhaskar@gmail.com>
Subject: [PATCH] arch: mips: kernel: Made couple of spelling fixes and a sentence construction in smp.c
Date: Mon, 1 Feb 2021 16:47:57 +0530 [thread overview]
Message-ID: <20210201111757.8019-1-unixbhaskar@gmail.com> (raw)
s/intercpu/inter CPU/
s/debugees/debuge's/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
arch/mips/kernel/smp.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/mips/kernel/smp.c b/arch/mips/kernel/smp.c
index 74b9102fd06e..e8a4ce7330ab 100644
--- a/arch/mips/kernel/smp.c
+++ b/arch/mips/kernel/smp.c
@@ -59,7 +59,7 @@ static DECLARE_COMPLETION(cpu_starting);
static DECLARE_COMPLETION(cpu_running);
/*
- * A logcal cpu mask containing only one VPE per core to
+ * A logical cpu mask containing only one VPE per core to
* reduce the number of IPIs on large MT systems.
*/
cpumask_t cpu_foreign_map[NR_CPUS] __read_mostly;
@@ -510,10 +510,10 @@ static inline void smp_on_each_tlb(void (*func) (void *info), void *info)
* address spaces, a new context is obtained on the current cpu, and tlb
* context on other cpus are invalidated to force a new context allocation
* at switch_mm time, should the mm ever be used on other cpus. For
- * multithreaded address spaces, intercpu interrupts have to be sent.
- * Another case where intercpu interrupts are required is when the target
+ * multithreaded address spaces, inter CPU interrupts have to be sent.
+ * Another case where inter CPU interrupts are required is when the target
* mm might be active on another cpu (eg debuggers doing the flushes on
- * behalf of debugees, kswapd stealing pages from another process etc).
+ * behalf of debuge's, kswapd stealing pages from another process etc).
* Kanoj 07/00.
*/
--
2.26.2
next reply other threads:[~2021-02-01 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 11:17 Bhaskar Chowdhury [this message]
2021-02-01 16:51 ` [PATCH] arch: mips: kernel: Made couple of spelling fixes and a sentence construction in smp.c Bert Vermeulen
2021-02-01 17:51 ` Randy Dunlap
2021-02-01 23:39 ` Bhaskar Chowdhury
2021-02-01 23:38 ` Bhaskar Chowdhury
2021-02-13 23:49 ` Maciej W. Rozycki
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=20210201111757.8019-1-unixbhaskar@gmail.com \
--to=unixbhaskar@gmail.com \
--cc=afzal.mohd.ma@gmail.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=tsbogend@alpha.franken.de \
/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