From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>, Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/4] signal.7: tfix
Date: Wed, 23 Dec 2020 20:42:16 +0100 [thread overview]
Message-ID: <16ce14af-9593-9ada-a745-d70e6ff81b1d@gmail.com> (raw)
In-Reply-To: <20201223193033.1012-1-jwilk@jwilk.net>
On 12/23/20 8:30 PM, Jakub Wilk wrote:
> Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
Jakub, patch applied.
Thanks,
Alex
> ---
> 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
>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2020-12-23 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 19:30 [PATCH 1/4] signal.7: tfix Jakub Wilk
2020-12-23 19:30 ` [PATCH 2/4] cgroups.7: tfix Jakub Wilk
2020-12-23 19:51 ` Alejandro Colomar (man-pages)
2020-12-23 19:30 ` [PATCH 3/4] ftime.3: tfix Jakub Wilk
2020-12-23 19:40 ` Alejandro Colomar (man-pages)
2020-12-23 19:30 ` [PATCH 4/4] filesystems.5: tfix Jakub Wilk
2020-12-23 23:58 ` Alejandro Colomar (man-pages)
2020-12-23 19:42 ` Alejandro Colomar (man-pages) [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-28 9:42 [PATCH 1/4] signal.7: 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=16ce14af-9593-9ada-a745-d70e6ff81b1d@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