From: "tip-bot2 for Ethon Paul" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Ethon Paul <ethp@qq.com>, Thomas Gleixner <tglx@linutronix.de>,
x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [tip: smp/core] cpu/hotplug: Fix a typo in comment "broadacasted"->"broadcasted"
Date: Mon, 27 Apr 2020 20:44:28 -0000 [thread overview]
Message-ID: <158802026848.28353.13219786488498822850.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200417164008.6541-1-ethp@qq.com>
The following commit has been merged into the smp/core branch of tip:
Commit-ID: 182e073f68a080a29920f6dca796ccf4806b0329
Gitweb: https://git.kernel.org/tip/182e073f68a080a29920f6dca796ccf4806b0329
Author: Ethon Paul <ethp@qq.com>
AuthorDate: Sat, 18 Apr 2020 00:40:04 +08:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Mon, 27 Apr 2020 22:42:04 +02:00
cpu/hotplug: Fix a typo in comment "broadacasted"->"broadcasted"
Signed-off-by: Ethon Paul <ethp@qq.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lkml.kernel.org/r/20200417164008.6541-1-ethp@qq.com
---
kernel/cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
index 2371292..6a02d44 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -432,7 +432,7 @@ static inline bool cpu_smt_allowed(unsigned int cpu)
/*
* On x86 it's required to boot all logical CPUs at least once so
* that the init code can get a chance to set CR4.MCE on each
- * CPU. Otherwise, a broadacasted MCE observing CR4.MCE=0b on any
+ * CPU. Otherwise, a broadcasted MCE observing CR4.MCE=0b on any
* core will shutdown the machine.
*/
return !cpumask_test_cpu(cpu, &cpus_booted_once_mask);
parent reply other threads:[~2020-04-27 20:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200417164008.6541-1-ethp@qq.com>]
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=158802026848.28353.13219786488498822850.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=ethp@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).