From be232513a2609bb48dd10791e58518ba93c12ea1 Mon Sep 17 00:00:00 2001
From: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Sun, 20 Nov 2016 21:05:26 +0100
Subject: [PATCH] mprotect.2: srcfix: rewrap source lines

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
---
 man2/mprotect.2 | 34 +++++++++++++++++++++++-----------
 1 file changed, 23 insertions(+), 11 deletions(-)

diff --git a/man2/mprotect.2 b/man2/mprotect.2
index 8f4c09f4b..d7ffd76d2 100644
--- a/man2/mprotect.2
+++ b/man2/mprotect.2
@@ -71,7 +71,8 @@ The memory can be modified.
 The memory can be executed.
 .TP
 .BR PROT_SEM " (since Linux 2.5.7)"
-The memory can be used for atomic operations. It was introduced as part of
+The memory can be used for atomic operations.
+It was introduced as part of
 .BR futex (2)
 implementation (in order to guarantee ability to perform atomic
 operations required by its commands such as
@@ -80,9 +81,11 @@ but not actually used in any currently supported architecture so far.
 .\" aba46c5027cb59d98052231b36efcbbde9c77a1d ef3d3246a0d06be622867d21af25f997aeeb105f
 .TP
 .BR PROT_SAO " (since Linux 2.6.26)"
-The memory should have strong access ordering. This feature is specific to
-PowerPC architecture (version 2.06 of architecture specification adds SAO CPU
-feature, and it is available on POWER 7 or PowerPC A2, for example).
+The memory should have strong access ordering.
+This feature is specific to
+PowerPC architecture
+(version 2.06 of architecture specification adds SAO CPU feature,
+and it is available on POWER 7 or PowerPC A2, for example).
 .PP
 Additionally (since Linux 2.6.0),
 .I prot
@@ -93,14 +96,15 @@ can have one of the following flags set:
 .\"			mm->def_flags | VM_MAYREAD | VM_MAYWRITE | VM_MAYEXEC;
 .\" And calc_vm_flag_bits converts only GROWSDOWN/DENYWRITE/LOCKED.
 .B PROT_GROWSUP
-Apply protection mode up to the end of the mapping which grows up (it should be a
-stack segment on HP PA-RISC, since there are no other ways to map a segment with
+Apply protection mode up to the end of the mapping which grows up
+(it should be a stack segment on HP PA-RISC,
+since there are no other ways to map a segment with
 .B VM_GROWSUP
 even if architecture has support for it.)
 .TP
 .B PROT_GROWSDOWN
-Apply protection mode down to the beginning of the mapping which grows down (it
-should be stack segment or mapped with
+Apply protection mode down to the beginning of the mapping which grows down
+(it should be stack segment or mapped with
 .B MAP_GROWSDOWN
 flag set.)
 .PP
@@ -153,14 +157,22 @@ or not a multiple of the system page size.
 .TP
 .BR EINVAL
 Both
-.BR PROT_GROWSUP " and " PROT_GROWSDOWN
+.BR PROT_GROWSUP
+and
+.BR PROT_GROWSDOWN
 were specified in
 .IR prot .
 .TP
 .BR EINVAL
 Invalid (other than
-.BR PROT_READ ", " PROT_WRITE ", " PROT_EXEC ", " PROT_SEM ", "
-.BR PROT_SAO " (on PowerPC only), " PROT_GROWSUP ", " PROT_GROWSDOWN )
+.BR PROT_READ ,
+.BR PROT_WRITE ,
+.BR PROT_EXEC ,
+.BR PROT_SEM ,
+.BR PROT_SAO
+(on PowerPC only),
+.BR PROT_GROWSUP ,
+.BR PROT_GROWSDOWN )
 flags specified in
 .IR prot .
 .TP