Merging upstream version 4.23.0.

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

1 files changed, 5 insertions, 5 deletions

diff --git a/upstream/debian-unstable/man7/thread-keyring.7 b/upstream/debian-unstable/man7/thread-keyring.7
index 524bf227..ceefb4a4 100644
--- a/upstream/debian-unstable/man7/thread-keyring.7
+++ b/upstream/debian-unstable/man7/thread-keyring.7
@@ -3,7 +3,7 @@
 .\"
 .\" SPDX-License-Identifier: GPL-2.0-or-later
 .\"
-.TH thread-keyring 7 2022-10-30 "Linux man-pages 6.05.01"
+.TH thread-keyring 7 2024-05-02 "Linux man-pages 6.8"
 .SH NAME
 thread-keyring \- per-thread keyring
 .SH DESCRIPTION
@@ -11,19 +11,19 @@ The thread keyring is a keyring used to anchor keys on behalf of a process.
 It is created only when a thread requests it.
 The thread keyring has the name (description)
 .IR _tid .
-.PP
+.P
 A special serial number value,
 .BR KEY_SPEC_THREAD_KEYRING ,
 is defined that can be used in lieu of the actual serial number of
 the calling thread's thread keyring.
-.PP
+.P
 From the
 .BR keyctl (1)
 utility, '\fB@t\fP' can be used instead of a numeric key ID in
 much the same way, but as
 .BR keyctl (1)
 is a program run after forking, this is of no utility.
-.PP
+.P
 Thread keyrings are not inherited across
 .BR clone (2)
 and
@@ -31,7 +31,7 @@ and
 and are cleared by
 .BR execve (2).
 A thread keyring is destroyed when the thread that refers to it terminates.
-.PP
+.P
 Initially, a thread does not have a thread keyring.
 If a thread doesn't have a thread keyring when it is accessed,
 then it will be created if it is to be modified;