Merging upstream version 6.7.

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

1 files changed, 6 insertions, 6 deletions

diff --git a/man7/fifo.7 b/man7/fifo.7
index f27dcc7..6241a43 100644
--- a/man7/fifo.7
+++ b/man7/fifo.7
@@ -4,7 +4,7 @@
 .\"
 .\" 990620 - page created - aeb@cwi.nl
 .\"
-.TH fifo 7 2023-07-15 "Linux man-pages 6.05.01"
+.TH fifo 7 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 fifo \- first-in first-out special file, named pipe
 .SH DESCRIPTION
@@ -19,14 +19,14 @@ Thus, the FIFO special file has no
 contents on the filesystem; the filesystem entry merely
 serves as a reference point so that processes can access
 the pipe using a name in the filesystem.
-.PP
+.P
 The kernel maintains exactly one pipe object for each
 FIFO special file that is opened by at least one process.
 The FIFO must be opened on both ends (reading and writing)
 before data can be passed.
 Normally, opening the FIFO blocks
 until the other end is opened also.
-.PP
+.P
 A process can open a FIFO in nonblocking mode.
 In this
 case, opening for read-only succeeds even if no one has
@@ -35,7 +35,7 @@ fails with
 .B ENXIO
 (no such device or address) unless the other
 end has already been opened.
-.PP
+.P
 Under Linux, opening a FIFO for read and write will succeed
 both in blocking and nonblocking mode.
 POSIX leaves this
@@ -48,12 +48,12 @@ with itself should be very careful to avoid deadlocks.
 .SH NOTES
 For details of the semantics of I/O on FIFOs, see
 .BR pipe (7).
-.PP
+.P
 When a process tries to write to a FIFO that is not opened
 for read on the other side, the process is sent a
 .B SIGPIPE
 signal.
-.PP
+.P
 FIFO special files can be created by
 .BR mkfifo (3),
 and are indicated by