Documentation: core-api: real-time: correct spelling
Subsystems (2)
PATCH 1/1 Documentation: core-api: real-time: correct spelling
Fix typo "excpetion" with "exception".
Signed-off-by Sukrut Heroorkar <[email protected]>
--- Documentation/core-api/real-time/architecture-porting.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/core-api/real-time/architecture-porting.rst +1 -1
@@ -74,7 +74,7 @@ Exception handlers Enabling interrupts is especially important on PREEMPT_RT, where certain locks, such as spinlock_t, become sleepable. For example, handling an invalid opcode may result in sending a SIGILL signal to the user task. A - debug excpetion will send a SIGTRAP signal. + debug exception will send a SIGTRAP signal. In both cases, if the exception occurred in user space, it is safe to enable interrupts early. Sending a signal requires both interrupts and kernel preemption to be enabled.
Signature · 1 line
2.43.0
Quoted 12 lines · Sukrut Heroorkar
Fix typo "excpetion" with "exception".
Signed-off-by Sukrut Heroorkar <[email protected]>--- Documentation/core-api/real-time/architecture-porting.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/core-api/real-time/architecture-porting.rst +0
-0
Documentation/core-api/real-time/architecture-porting.rst Exception handlers · line 78
Quoted 6 lines
Documentation/core-api/real-time/architecture-porting.rst +1
-1@@ -74,7 +74,7 @@ Exception handlers Enabling interrupts is especially important on PREEMPT_RT, where certain locks, such as spinlock_t, become sleepable. For example, handling an invalid opcode may result in sending a SIGILL signal to the user task. A - debug excpetion will send a SIGTRAP signal. + debug exception will send a SIGTRAP signal. In both cases, if the exception occurred in user space, it is safe to enable
Applied, thanks.
jon