linux-kernel - [PATCH] xtensa: Fix spelling/grammar in comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200525230413.15551-1-chris.packham@alliedtelesis.co.nz>
Date:   Tue, 26 May 2020 11:04:13 +1200
From:   Chris Packham <chris.packham@...iedtelesis.co.nz>
To:     0001-xtensa-Fix-spelling-grammar-in-comment.patch@...iedtelesis.co.nz
Cc:     linux-xtensa@...ux-xtensa.org, linux-kernel@...r.kernel.org,
        trivial@...nel.org,
        Chris Packham <chris.packham@...iedtelesis.co.nz>,
        Chris Zankel <chris@...kel.net>,
        Max Filippov <jcmvbkbc@...il.com>
Subject: [PATCH] xtensa: Fix spelling/grammar in comment

Change 'excpetion' to 'exception', 'handeled' to 'handled' and 'the the'
to 'the'.

Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
---
 arch/xtensa/kernel/entry.S | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/xtensa/kernel/entry.S b/arch/xtensa/kernel/entry.S
index 06fbb0a171f1..696b1e4b1a67 100644
--- a/arch/xtensa/kernel/entry.S
+++ b/arch/xtensa/kernel/entry.S
@@ -959,14 +959,14 @@ ENDPROC(unrecoverable_exception)
  * of the proper size instead.
  *
  * This algorithm simply backs out the register changes started by the user
- * excpetion handler, makes it appear that we have started a window underflow
+ * exception handler, makes it appear that we have started a window underflow
  * by rotating the window back and then setting the old window base (OWB) in
  * the 'ps' register with the rolled back window base. The 'movsp' instruction
  * will be re-executed and this time since the next window frames is in the
  * active AR registers it won't cause an exception.
  *
  * If the WindowUnderflow code gets a TLB miss the page will get mapped
- * the the partial windeowUnderflow will be handeled in the double exception
+ * the partial windeowUnderflow will be handled in the double exception
  * handler.
  *
  * Entry condition:
-- 
2.25.1