[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190902102436.27396-2-marco.ammon@fau.de>
Date: Mon, 2 Sep 2019 12:24:35 +0200
From: Marco Ammon <marco.ammon@....de>
To: linux-kernel@...r.kernel.org
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
trivial@...nel.org, Marco Ammon <marco.ammon@....de>
Subject: [PATCH 2/3] x86: fix typo in comment for alternative_instructions
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@....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
Powered by blists - more mailing lists