]> git.ipfire.org Git - thirdparty/kernel/linux.git/commitdiff
x86/entry: Fix typos in comments
authorXin Li (Intel) <xin@zytor.com>
Tue, 26 Sep 2023 06:13:19 +0000 (23:13 -0700)
committerIngo Molnar <mingo@kernel.org>
Wed, 27 Sep 2023 08:05:04 +0000 (10:05 +0200)
Fix 2 typos in the comments.

Signed-off-by: Xin Li (Intel) <xin@zytor.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: H. Peter Anvin (Intel) <hpa@zytor.com>
Link: https://lore.kernel.org/r/20230926061319.1929127-1-xin@zytor.com
arch/x86/entry/entry_64.S

index fb8dd5648e3ac7dad191345bcc35df9470425b0e..b940e928c808848142b2eec708149ccfca7aaa47 100644 (file)
@@ -1163,8 +1163,8 @@ SYM_CODE_START(asm_exc_nmi)
         * anyway.
         *
         * To handle this case we do the following:
-        *  Check the a special location on the stack that contains
-        *  variable that is set when NMIs are executing.
+        *  Check a special location on the stack that contains a
+        *  variable that is set when NMIs are executing.
         *  The interrupted task's stack is also checked to see if it
         *  is an NMI stack.
         *  If the variable is not set and the stack is not the NMI
@@ -1294,8 +1294,8 @@ SYM_CODE_START(asm_exc_nmi)
         * end_repeat_nmi, then we are a nested NMI.  We must not
         * modify the "iret" frame because it's being written by
         * the outer NMI.  That's okay; the outer NMI handler is
-        * about to about to call exc_nmi() anyway, so we can just
-        * resume the outer NMI.
+        * about to call exc_nmi() anyway, so we can just resume
+        * the outer NMI.
         */
 
        movq    $repeat_nmi, %rdx