From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Jakub Wilk <jwilk@jwilk.net>,
linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>
Subject: [PATCH v2 1/4] signal.7: tfix
Date: Tue, 29 Dec 2020 21:37:45 +0100 [thread overview]
Message-ID: <20201229203747.3199-2-alx.manpages@gmail.com> (raw)
In-Reply-To: <20201228094211.4917-4-alx.manpages@gmail.com>
From: Jakub Wilk <jwilk@jwilk.net>
Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
man7/signal.7 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man7/signal.7 b/man7/signal.7
index e5b9e00ca..1b48356b8 100644
--- a/man7/signal.7
+++ b/man7/signal.7
@@ -357,7 +357,7 @@ From the kernel's point of view,
execution of the signal handler code is exactly the same as the execution
of any other user-space code.
That is to say, the kernel does not record any special state information
-indicating that the thread is currently excuting inside a signal handler.
+indicating that the thread is currently executing inside a signal handler.
All necessary state information is maintained in user-space registers
and the user-space stack.
The depth to which nested signal handlers may be invoked is thus
--
2.29.2
next prev parent reply other threads:[~2020-12-29 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 9:42 [PATCH 1/4] signal.7: tfix Alejandro Colomar
2020-12-28 9:42 ` [PATCH 2/4] cgroups.7: tfix Alejandro Colomar
2020-12-28 9:42 ` [PATCH 3/4] ftime.3: tfix Alejandro Colomar
2020-12-28 9:42 ` [PATCH 4/4] filesystems.5: tfix Alejandro Colomar
2020-12-29 20:37 ` [PATCH v2 0/4] Resend signed Alejandro Colomar
2020-12-30 8:31 ` Michael Kerrisk (man-pages)
2020-12-29 20:37 ` Alejandro Colomar [this message]
2020-12-29 20:37 ` [PATCH v2 2/4] cgroups.7: tfix Alejandro Colomar
2020-12-29 20:37 ` [PATCH v2 3/4] ftime.3: tfix Alejandro Colomar
2020-12-29 20:37 ` [PATCH v2 4/4] filesystems.5: tfix Alejandro Colomar
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=20201229203747.3199-2-alx.manpages@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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