The branch main has been updated by imp:

URL: 
https://cgit.FreeBSD.org/src/commit/?id=8551c31b2eee1bb10ad6bbd38f413e483447fc6f

commit 8551c31b2eee1bb10ad6bbd38f413e483447fc6f
Author:     Elyes Haouas <[email protected]>
AuthorDate: 2024-04-11 17:27:29 +0000
Commit:     Warner Losh <[email protected]>
CommitDate: 2024-04-11 17:28:25 +0000

    exception: Fix typos
    
    Signed-off-by: Elyes Haouas <[email protected]>
    Reviewed by: imp
    Pull Request: https://github.com/freebsd/freebsd-src/pull/885
---
 sys/amd64/amd64/exception.S | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/sys/amd64/amd64/exception.S b/sys/amd64/amd64/exception.S
index 90f7a88f5d52..7b6cde824203 100644
--- a/sys/amd64/amd64/exception.S
+++ b/sys/amd64/amd64/exception.S
@@ -207,7 +207,7 @@ X\l:
         * alltraps_u/k entry points.
         * SWAPGS must be already performed by prologue,
         * if this is the first time in the kernel from userland.
-        * Reenable interrupts if they were enabled before the trap.
+        * Re-enable interrupts if they were enabled before the trap.
         * This approximates SDT_SYS386TGT on the i386 port.
         */
        SUPERALIGN_TEXT
@@ -512,7 +512,7 @@ prot_addrf:
 
 /*
  * Fast syscall entry point.  We enter here with just our new %cs/%ss set,
- * and the new privilige level.  We are still running on the old user stack
+ * and the new privilege level.  We are still running on the old user stack
  * pointer.  We have to juggle a few things around to find our stack etc.
  * swapgs gives us access to our PCPU space only.
  *
@@ -1087,7 +1087,7 @@ ENTRY(fork_trampoline)
  * and bintr, and only interrupt handlers between the labels bintr and
  * eintr.  This is implemented (partly) by including files that contain
  * some of the handlers.  Before including the files, set up a normal asm
- * environment so that the included files doen't need to know that they are
+ * environment so that the included files doesn't need to know that they are
  * included.
  */
 

Reply via email to