From: Marco Ammon <marco.ammon@fau.de>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, trivial@kernel.org,
Marco Ammon <marco.ammon@fau.de>
Subject: [PATCH 2/3] x86: fix typo in comment for alternative_instructions
Date: Mon, 2 Sep 2019 12:24:35 +0200 [thread overview]
Message-ID: <20190902102436.27396-2-marco.ammon@fau.de> (raw)
In-Reply-To: <20190902102436.27396-1-marco.ammon@fau.de>
In the documentation for alternative_instructions, "a unlikely" should
actually be "an unlikely". This patch fixes the mistake.
Signed-off-by: Marco Ammon <marco.ammon@fau.de>
---
arch/x86/kernel/alternative.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c
index 0eefd497e3d8..9d3a971ea364 100644
--- a/arch/x86/kernel/alternative.c
+++ b/arch/x86/kernel/alternative.c
@@ -713,7 +713,7 @@ void __init alternative_instructions(void)
* Don't stop machine check exceptions while patching.
* MCEs only happen when something got corrupted and in this
* case we must do something about the corruption.
- * Ignoring it is worse than a unlikely patching race.
+ * Ignoring it is worse than an unlikely patching race.
* Also machine checks tend to be broadcast and if one CPU
* goes into machine check the others follow quickly, so we don't
* expect a machine check to cause undue problems during to code
--
2.23.0
next prev parent reply other threads:[~2019-09-02 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 10:24 [PATCH 1/3] x86: fix typo in comment for poke_text_early Marco Ammon
2019-09-02 10:24 ` Marco Ammon [this message]
2019-09-02 10:24 ` [PATCH 3/3] x86: kprobes: fix typo in comment Marco Ammon
2019-09-02 12:10 ` [PATCH 1/3] x86: fix typo in comment for poke_text_early Borislav Petkov
2019-09-02 12:14 ` [tip: x86/cleanups] x86: Correct misc typos tip-bot2 for Marco Ammon
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=20190902102436.27396-2-marco.ammon@fau.de \
--to=marco.ammon@fau.de \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=trivial@kernel.org \
--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