Adding upstream version 4.23.0.upstream/4.23.0

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 5 insertions, 5 deletions

diff --git a/upstream/opensuse-tumbleweed/man2/restart_syscall.2 b/upstream/opensuse-tumbleweed/man2/restart_syscall.2
index 4b0e1014..8c752d4e 100644
--- a/upstream/opensuse-tumbleweed/man2/restart_syscall.2
+++ b/upstream/opensuse-tumbleweed/man2/restart_syscall.2
@@ -10,14 +10,14 @@
 .\"
 .\" See also Section 11.3.3 of Understanding the Linux Kernel, 3rd edition
 .\"
-.TH restart_syscall 2 2023-03-30 "Linux man-pages 6.05.01"
+.TH restart_syscall 2 2024-05-02 "Linux man-pages (unreleased)"
 .SH NAME
 restart_syscall \- restart a system call after interruption by a stop signal
 .SH SYNOPSIS
 .nf
 .B long restart_syscall(void);
 .fi
-.PP
+.P
 .IR Note :
 There is no glibc wrapper for this system call; see NOTES.
 .SH DESCRIPTION
@@ -32,7 +32,7 @@ is later resumed after receiving a
 .B SIGCONT
 signal.
 This system call is designed only for internal use by the kernel.
-.PP
+.P
 .BR restart_syscall ()
 is used for restarting only those system calls that,
 when restarted, should adjust their time-related parameters\[em]namely
@@ -83,7 +83,7 @@ Linux 2.6.
 There is no glibc wrapper for this system call,
 because it is intended for use only by the kernel and
 should never be called by applications.
-.PP
+.P
 The kernel uses
 .BR restart_syscall ()
 to ensure that when a system call is restarted
@@ -105,7 +105,7 @@ Notable examples of system calls that suffer this problem are
 .BR select (2),
 and
 .BR pselect (2).
-.PP
+.P
 From user space, the operation of
 .BR restart_syscall ()
 is largely invisible: