sendfile.2, vfork.2, alloca.3, getcontext.3, tmpfs.5, ttytype.5, spufs.7: ffix

Break lines containing two man page references into a line for each.
This is not only more consistent with our guidelines (man-pages(7));
it also helps prepare for the future adoption of the MR man(7) macro.

Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

diff --git a/man2/sendfile.2 b/man2/sendfile.2
index 2ecbdbbb7e1d6f9c4958da93698a9dc96e577a84..a50f2797a4848d36b491bc138ef0bdea17a6152c 100644 (file)
--- a/man2/sendfile.2
+++ b/man2/sendfile.2
@@ -212,7 +212,9 @@ The glibc
 wrapper function transparently deals with the kernel differences.
 .PP
 Applications may wish to fall back to
-.BR read (2)/ write (2)
+.BR read (2)
+and
+.BR write (2)
 in the case where
 .BR sendfile ()
 fails with

diff --git a/man2/vfork.2 b/man2/vfork.2
index d4207a5dbc8d6f09e9a9bc432262bfd75b29fb41..1414ba80f375d995701f2a57c156139a7b75d531 100644 (file)
--- a/man2/vfork.2
+++ b/man2/vfork.2
@@ -182,7 +182,8 @@ from the standard; the POSIX rationale for the
 .BR posix_spawn (3)
 function notes that that function,
 which provides functionality equivalent to
-.BR fork (2)+ exec (3),
+.BR fork (2)+\c
+.BR exec (3),
 is designed to be implementable on systems that lack an MMU.)
 .\" http://stackoverflow.com/questions/4259629/what-is-the-difference-between-fork-and-vfork
 .\" http://developers.sun.com/solaris/articles/subprocess/subprocess.html

diff --git a/man3/alloca.3 b/man3/alloca.3
index 576deb48356c592ba3b4f2d160b53bcb00801e48..e62d99b58e8fac7268663baaaa5b35c95e3a7cb6 100644 (file)
--- a/man3/alloca.3
+++ b/man3/alloca.3
@@ -66,7 +66,9 @@ The
 .BR alloca ()
 function is machine- and compiler-dependent.
 Because it allocates from the stack, it's faster than
-.BR malloc (3)/ free (3).
+.BR malloc (3)
+and
+.BR free (3).
 In certain cases,
 it can also simplify memory deallocation in applications that use
 .BR longjmp (3)

diff --git a/man3/getcontext.3 b/man3/getcontext.3
index 4b31b17c55afa5fcd717f71ea06f9972ee37ddb1..b4a4766bac23f292f339500ba28e61c1bd9f5bfd 100644 (file)
--- a/man3/getcontext.3
+++ b/man3/getcontext.3
@@ -163,11 +163,13 @@ citing portability issues, and
 recommending that applications be rewritten to use POSIX threads instead.
 .SH NOTES
 The earliest incarnation of this mechanism was the
-.BR setjmp (3)/ longjmp (3)
+.BR setjmp (3)/\c
+.BR longjmp (3)
 mechanism.
 Since that does not define
 the handling of the signal context, the next stage was the
-.BR sigsetjmp (3)/ siglongjmp (3)
+.BR sigsetjmp (3)/\c
+.BR siglongjmp (3)
 pair.
 The present mechanism gives much more control.
 On the other hand,

diff --git a/man5/tmpfs.5 b/man5/tmpfs.5
index f7bf5a6025a8122ae923e1deac14a775484c3705..1efdbd5fc3917236affb1c0afe4ddf6ec9a6e522 100644 (file)
--- a/man5/tmpfs.5
+++ b/man5/tmpfs.5
@@ -134,12 +134,16 @@ Attempt to allocate huge pages every time a new page is needed.
 Only allocate huge page if it will be fully within
 .IR i_size .
 Also respect
-.BR fadvise (2)/ madvise (2)
+.BR fadvise (2)
+and
+.BR madvise (2)
 hints
 .TP
 .B advise
 Only allocate huge pages if requested with
-.BR fadvise (2)/ madvise (2).
+.BR fadvise (2)
+or
+.BR madvise (2).
 .TP
 .B deny
 For use in emergencies, to force the huge option off from all mounts.

diff --git a/man5/ttytype.5 b/man5/ttytype.5
index f08aa5c7ac4368520035331639c95e3c28594227..356c26d721dc9ce9d8f1bdaee622504553f2cec8 100644 (file)
--- a/man5/ttytype.5
+++ b/man5/ttytype.5
@@ -14,7 +14,9 @@ ttytype \- terminal device to default terminal type mapping
 The
 .I /etc/ttytype
 file associates
-.BR termcap (5)/ terminfo (5)
+.BR termcap (5)
+and
+.BR terminfo (5)
 terminal type names
 with tty lines.
 Each line consists of a terminal type, followed by

diff --git a/man7/spufs.7 b/man7/spufs.7
index f012d082066628d766cb1b239c552d555ba3b642..2fd2d13d07090a6e808abe7ff43410959816dc03 100644 (file)
--- a/man7/spufs.7
+++ b/man7/spufs.7
@@ -82,9 +82,11 @@ and
 .IR st_gid .
 .PP
 All files support the
-.BR chmod (2)/ fchmod (2)
+.BR chmod (2)/\c
+.BR fchmod (2)
 and
-.BR chown (2)/ fchown (2)
+.BR chown (2)/\c
+.BR fchown (2)
 operations, but will not be able to grant permissions that contradict
 the possible operations (e.g., read access on the
 .I wbox