public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 1/4] signal.7: tfix
@ 2020-12-28  9:42 Alejandro Colomar
  2020-12-28  9:42 ` [PATCH 2/4] cgroups.7: tfix Alejandro Colomar
                   ` (2 more replies)
  0 siblings, 3 replies; 12+ messages in thread
From: Alejandro Colomar @ 2020-12-28  9:42 UTC (permalink / raw)
  To: mtk.manpages; +Cc: Jakub Wilk, linux-man

From: Jakub Wilk <jwilk@jwilk.net>

Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
---

Hi Michael,

Here are some tfixes I merged from Jakub.

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
-- 
2.29.2


^ permalink raw reply related	[flat|nested] 12+ messages in thread
* [PATCH 1/4] signal.7: tfix
@ 2020-12-23 19:30 Jakub Wilk
  2020-12-23 19:30 ` [PATCH 3/4] ftime.3: tfix Jakub Wilk
  0 siblings, 1 reply; 12+ messages in thread
From: Jakub Wilk @ 2020-12-23 19:30 UTC (permalink / raw)
  To: Michael Kerrisk; +Cc: linux-man

Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
---
 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.30.0.rc1


^ permalink raw reply related	[flat|nested] 12+ messages in thread
end of thread, other threads:[~2020-12-30  8:32 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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   ` [PATCH v2 1/4] signal.7: tfix Alejandro Colomar
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
  -- strict thread matches above, loose matches on Subject: below --
2020-12-23 19:30 [PATCH 1/4] signal.7: tfix Jakub Wilk
2020-12-23 19:30 ` [PATCH 3/4] ftime.3: tfix Jakub Wilk
2020-12-23 19:40   ` Alejandro Colomar (man-pages)

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox