Merging upstream version 4.23.0.

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

1 files changed, 7 insertions, 7 deletions

diff --git a/upstream/debian-unstable/man2/timer_getoverrun.2 b/upstream/debian-unstable/man2/timer_getoverrun.2
index 75219572..5724354d 100644
--- a/upstream/debian-unstable/man2/timer_getoverrun.2
+++ b/upstream/debian-unstable/man2/timer_getoverrun.2
@@ -3,7 +3,7 @@
 .\"
 .\" SPDX-License-Identifier: Linux-man-pages-copyleft
 .\"
-.TH timer_getoverrun 2 2023-03-30 "Linux man-pages 6.05.01"
+.TH timer_getoverrun 2 2024-05-02 "Linux man-pages 6.8"
 .SH NAME
 timer_getoverrun \- get overrun count for a POSIX per-process timer
 .SH LIBRARY
@@ -12,15 +12,15 @@ Real-time library
 .SH SYNOPSIS
 .nf
 .B  #include <time.h>
-.PP
+.P
 .BI "int timer_getoverrun(timer_t " timerid );
 .fi
-.PP
+.P
 .RS -4
 Feature Test Macro Requirements for glibc (see
 .BR feature_test_macros (7)):
 .RE
-.PP
+.P
 .BR timer_getoverrun ():
 .nf
     _POSIX_C_SOURCE >= 199309L
@@ -36,7 +36,7 @@ via signals
 .RB ( SIGEV_SIGNAL ),
 and via threads
 .RB ( SIGEV_THREAD ).
-.PP
+.P
 When expiration notifications are delivered via a signal,
 overruns can occur as follows.
 Regardless of whether or not a real-time signal is used for
@@ -56,7 +56,7 @@ In this interval, further timer expirations may occur.
 The timer overrun count is the number of additional
 timer expirations that occurred between the time when the signal
 was generated and when it was delivered or accepted.
-.PP
+.P
 Timer overruns can also occur when expiration notifications
 are delivered via invocation of a thread,
 since there may be an arbitrary delay between an expiration of the timer
@@ -87,7 +87,7 @@ structure (see
 This allows an application to avoid the overhead of making
 a system call to obtain the overrun count,
 but is a nonportable extension to POSIX.1.
-.PP
+.P
 POSIX.1 discusses timer overruns only in the context of
 timer notifications using signals.
 .\" FIXME . Austin bug filed, 11 Feb 09