From: Jonathan Corbet <corbet@lwn.net>
To: Sukrut Heroorkar <hsukrut3@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Shuah Khan <skhan@linuxfoundation.org>,
"open list:Real-time Linux (PREEMPT_RT)"
<linux-rt-devel@lists.linux.dev>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Cc: Sukrut Heroorkar <hsukrut3@gmail.com>
Subject: Re: [PATCH] Documentation: core-api: real-time: correct spelling
Date: Sun, 12 Apr 2026 13:12:03 -0600 [thread overview]
Message-ID: <87jyucyovw.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260411155120.233357-1-hsukrut3@gmail.com>
Sukrut Heroorkar <hsukrut3@gmail.com> writes:
> Fix typo "excpetion" with "exception".
>
> Signed-off-by: Sukrut Heroorkar <hsukrut3@gmail.com>
> ---
> Documentation/core-api/real-time/architecture-porting.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/real-time/architecture-porting.rst b/Documentation/core-api/real-time/architecture-porting.rst
> index c90a426d8062..c9a39d708866 100644
> --- a/Documentation/core-api/real-time/architecture-porting.rst
> +++ b/Documentation/core-api/real-time/architecture-porting.rst
> @@ -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
prev parent reply other threads:[~2026-04-12 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 15:51 [PATCH] Documentation: core-api: real-time: correct spelling Sukrut Heroorkar
2026-04-12 19:12 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jyucyovw.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=hsukrut3@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox