Removed trailing white space at end of lines

This commit is contained in:
Michael Kerrisk 2013-03-05 18:22:04 +01:00
parent fee1593ec4
commit b072a7882a
10 changed files with 16 additions and 16 deletions

View File

@ -61,7 +61,7 @@ is not NULL;
otherwise, no data is copied, and the call succeeds, otherwise, no data is copied, and the call succeeds,
returning the size that would be needed to store the unwind data. returning the size that would be needed to store the unwind data.
The first part of the unwind data contains an unwind table. The first part of the unwind data contains an unwind table.
The rest contains the associated unwind information, in no particular order. The rest contains the associated unwind information, in no particular order.
The unwind table contains entries of the following form: The unwind table contains entries of the following form:
@ -89,7 +89,7 @@ is set to indicate the error.
fails with the error fails with the error
.B EFAULT .B EFAULT
if the unwind info can't be stored in the space specified by if the unwind info can't be stored in the space specified by
.IR buf . .IR buf .
.SH VERSIONS .SH VERSIONS
This system call is available since Linux 2.4. This system call is available since Linux 2.4.
.SH CONFORMING TO .SH CONFORMING TO

View File

@ -614,10 +614,10 @@ for this case.
POSIX specifies that the system shall always POSIX specifies that the system shall always
zero fill any partial page at the end zero fill any partial page at the end
of the object and that system will never write any modification of the of the object and that system will never write any modification of the
object beyond its end. object beyond its end.
On Linux, when you write data to such partial page after the end On Linux, when you write data to such partial page after the end
of the object, the data stays in the page cache even after the file of the object, the data stays in the page cache even after the file
is closed and unmapped is closed and unmapped
and even though the data is never written to the file itself, and even though the data is never written to the file itself,
subsequent mappings may see the modified content. subsequent mappings may see the modified content.

View File

@ -101,7 +101,7 @@ in the low order 16 bits:
.\" mount --make-rshared ==> MS_SHARED | MS_REC .\" mount --make-rshared ==> MS_SHARED | MS_REC
.\" .\"
.\" These settings are visible in proc/mountinfo .\" These settings are visible in proc/mountinfo
.\" .\"
.\" .\"
.\" These need to be documented on this page. .\" These need to be documented on this page.
.\" See: .\" See:
@ -123,8 +123,8 @@ in the low order 16 bits:
.\" .\"
.\" Uncover practical applications for advanced Linux mounts features .\" Uncover practical applications for advanced Linux mounts features
.\" Serge E. Hallyn (sergeh@us.ibm.com), Software Engineer, IBM  .\" Serge E. Hallyn (sergeh@us.ibm.com), Software Engineer, IBM 
.\" Ram Pai (linuxram@us.ibm.com), Software Engineer, IBM .\" Ram Pai (linuxram@us.ibm.com), Software Engineer, IBM
.\" Date: 17 Sep 2007 .\" Date: 17 Sep 2007
.\" .\"
.\" 2.6.25 Added MS_I_VERSION, which needs to be documented. .\" 2.6.25 Added MS_I_VERSION, which needs to be documented.
.\" .\"

View File

@ -122,7 +122,7 @@ The
.I file creation flags .I file creation flags
are are
.BR O_CLOEXEC , .BR O_CLOEXEC ,
.BR O_CREAT , .BR O_CREAT ,
.BR O_DIRECTORY , .BR O_DIRECTORY ,
.BR O_EXCL , .BR O_EXCL ,
.BR O_NOCTTY , .BR O_NOCTTY ,

View File

@ -1054,10 +1054,10 @@ make_message(const char *fmt, ...)
va_end(ap); va_end(ap);
/* Check error code */ /* Check error code */
if (n < 0) if (n < 0)
return NULL; return NULL;
/* If that worked, return the string */ /* If that worked, return the string */
if (n < size) if (n < size)
@ -1066,7 +1066,7 @@ make_message(const char *fmt, ...)
/* Else try again with more space */ /* Else try again with more space */
size = n + 1; /* Precisely what is needed */ size = n + 1; /* Precisely what is needed */
if ((np = realloc (p, size)) == NULL) { if ((np = realloc (p, size)) == NULL) {
free(p); free(p);

View File

@ -89,7 +89,7 @@ precedence ::ffff:0:0/96 10
.fi .fi
.\" .SH AUTHOR .\" .SH AUTHOR
.\" Ulrich Drepper <drepper@redhat.com> .\" Ulrich Drepper <drepper@redhat.com>
.\" .\"
.SH SEE ALSO .SH SEE ALSO
.BR getaddrinfo(3), .BR getaddrinfo(3),
RFC\ 3484 RFC\ 3484

View File

@ -106,6 +106,6 @@ SERVICES_AUTHORITATIVE=FALSE
SETENT_BATCH_READ=FALSE SETENT_BATCH_READ=FALSE
.\" .SH AUTHOR .\" .SH AUTHOR
.\" Ulrich Drepper <drepper@redhat.com> .\" Ulrich Drepper <drepper@redhat.com>
.\" .\"
.SH SEE ALSO .SH SEE ALSO
\fInsswitch.conf\fR \fInsswitch.conf\fR

View File

@ -38,7 +38,7 @@ when writing man pages for the Linux \fIman-pages\fP project,
which documents the user-space API provided by the Linux kernel which documents the user-space API provided by the Linux kernel
and the GNU C library. and the GNU C library.
The project thus provides most of the pages in Section 2, The project thus provides most of the pages in Section 2,
as well as many of the pages that appear as well as many of the pages that appear
in Sections 3, 4, 5, and 7 of the man pages on a Linux system. in Sections 3, 4, 5, and 7 of the man pages on a Linux system.
The conventions described on this page may also be useful The conventions described on this page may also be useful
for authors writing man pages for other projects. for authors writing man pages for other projects.

View File

@ -144,7 +144,7 @@ is present.
.SS --- - _POSIX_FILE_LOCKING - _SC_FILE_LOCKING .SS --- - _POSIX_FILE_LOCKING - _SC_FILE_LOCKING
This option has been deleted. This option has been deleted.
Not in final XPG6. Not in final XPG6.
.SS FSC - _POSIX_FSYNC - _SC_FSYNC .SS FSC - _POSIX_FSYNC - _SC_FSYNC
The function The function
.IR fsync () .IR fsync ()
is present. is present.

View File

@ -314,7 +314,7 @@ this socket option could be set, but could not retrieved with
Since Linux 3.8, it is readable. Since Linux 3.8, it is readable.
The The
.I optlen .I optlen
argument should contain the buffer size available argument should contain the buffer size available
to receive the device name and is recommended to be to receive the device name and is recommended to be
.BR IFNAMSZ .BR IFNAMSZ
bytes. bytes.