[PATCH] man2/i*: srcfix: Use a single-font-change macro for a single argument

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  The output is unchanged, except the font change for a punctuation
mark (ioctl_userfaultfd.2).

Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
---
 man2/init_module.2         |  8 +++----
 man2/inotify_init.2        |  4 ++--
 man2/io_getevents.2        |  2 +-
 man2/io_submit.2           |  4 ++--
 man2/ioctl_console.2       |  4 ++--
 man2/ioctl_fat.2           |  6 ++---
 man2/ioctl_ficlonerange.2  | 18 +++++++-------
 man2/ioctl_fideduperange.2 | 42 ++++++++++++++++-----------------
 man2/ioctl_getfsmap.2      |  2 +-
 man2/ioctl_iflags.2        | 10 ++++----
 man2/ioctl_list.2          |  2 +-
 man2/ioctl_ns.2            | 16 ++++++-------
 man2/ioctl_tty.2           | 12 +++++-----
 man2/ioctl_userfaultfd.2   | 48 +++++++++++++++++++-------------------
 14 files changed, 89 insertions(+), 89 deletions(-)

diff --git a/man2/init_module.2 b/man2/init_module.2
index 4f13edf1f..a4d41318b 100644
--- a/man2/init_module.2
+++ b/man2/init_module.2
@@ -189,7 +189,7 @@ The caller was not privileged
 capability),
 or module loading is disabled
 (see
-.IR /proc/sys/kernel/modules_disabled
+.I /proc/sys/kernel/modules_disabled
 in
 .BR proc (5)).
 .PP
@@ -202,7 +202,7 @@ A module with this name is already loaded.
 .B EINVAL
 .I param_values
 is invalid, or some part of the ELF image in
-.IR module_image
+.I module_image
 contains inconsistencies.
 .\" .TP
 .\" .BR EINVAL " (Linux 2.4 and earlier)"
@@ -279,7 +279,7 @@ call it using
 .BR syscall (2).
 .PP
 Information about currently loaded modules can be found in
-.IR /proc/modules
+.I /proc/modules
 and in the file trees under the per-module subdirectories under
 .IR /sys/module .
 .PP
@@ -301,7 +301,7 @@ system call was rather different:
 is available by calling
 .BR query_module ();
 the latter call fails with the error
-.BR ENOSYS
+.B ENOSYS
 on Linux 2.6 and later.)
 .PP
 The older version of the system call
diff --git a/man2/inotify_init.2 b/man2/inotify_init.2
index 6ad994b93..62ec3282d 100644
--- a/man2/inotify_init.2
+++ b/man2/inotify_init.2
@@ -51,12 +51,12 @@ is 0, then
 is the same as
 .BR inotify_init ().
 The following values can be bitwise ORed in
-.IR flags
+.I flags
 to obtain different behavior:
 .TP 12
 .B IN_NONBLOCK
 Set the
-.BR O_NONBLOCK
+.B O_NONBLOCK
 file status flag on the open file description (see
 .BR open (2))
 referred to by the new file descriptor.
diff --git a/man2/io_getevents.2 b/man2/io_getevents.2
index 7a3e72094..54d4d18ba 100644
--- a/man2/io_getevents.2
+++ b/man2/io_getevents.2
@@ -119,7 +119,7 @@ indicating an error: \-1, with
 set to a (positive) value that indicates the error.
 .SH BUGS
 An invalid
-.IR ctx_id
+.I ctx_id
 may cause a segmentation fault instead of generating the error
 .BR EINVAL .
 .SH SEE ALSO
diff --git a/man2/io_submit.2 b/man2/io_submit.2
index c15db3f41..f0be7a0be 100644
--- a/man2/io_submit.2
+++ b/man2/io_submit.2
@@ -33,7 +33,7 @@ which will be submitted to context \fIctx_id\fP.
 The
 .I iocb
 (I/O control block) structure defined in
-.IR linux/aio_abi.h
+.I linux/aio_abi.h
 defines the parameters that control the I/O operation.
 .PP
 .in +4n
@@ -172,7 +172,7 @@ structure.
 The valid values are:
 .RS
 .TP
-.BR IOCB_FLAG_RESFD
+.B IOCB_FLAG_RESFD
 Asynchronous I/O control must signal the file
 descriptor mentioned in
 .I aio_resfd
diff --git a/man2/ioctl_console.2 b/man2/ioctl_console.2
index 4cac0bac2..af4b59d79 100644
--- a/man2/ioctl_console.2
+++ b/man2/ioctl_console.2
@@ -427,7 +427,7 @@ selects the key table (0 <=
 .I kb_table
 < MAX_NR_KEYMAPS),
 and
-.IR kb_index
+.I kb_index
 is the keycode (0 <=
 .I kb_index
 < NR_KEYS).
@@ -612,7 +612,7 @@ Release a display.
 .TP
 .B VT_ACTIVATE
 Switch to vt
-.IR argp
+.I argp
 (1 <=
 .I argp
 <= MAX_NR_CONSOLES).
diff --git a/man2/ioctl_fat.2 b/man2/ioctl_fat.2
index e1970b2ad..5f62acef1 100644
--- a/man2/ioctl_fat.2
+++ b/man2/ioctl_fat.2
@@ -225,14 +225,14 @@ does not refer to an object in a FAT filesystem.
 For further error values, see
 .BR ioctl (2).
 .SH VERSIONS
-.BR VFAT_IOCTL_READDIR_BOTH
+.B VFAT_IOCTL_READDIR_BOTH
 and
 .B VFAT_IOCTL_READDIR_SHORT
 first appeared in Linux 2.0.
 .PP
-.BR FAT_IOCTL_GET_ATTRIBUTES
+.B FAT_IOCTL_GET_ATTRIBUTES
 and
-.BR FAT_IOCTL_SET_ATTRIBUTES
+.B FAT_IOCTL_SET_ATTRIBUTES
 first appeared
 .\" just before we got Git history
 in Linux 2.6.12.
diff --git a/man2/ioctl_ficlonerange.2 b/man2/ioctl_ficlonerange.2
index d6db1bed4..3fde48fcf 100644
--- a/man2/ioctl_ficlonerange.2
+++ b/man2/ioctl_ficlonerange.2
@@ -49,18 +49,18 @@ written.
 This behavior is commonly referred to as "copy on write".
 .PP
 This ioctl reflinks up to
-.IR src_length
+.I src_length
 bytes from file descriptor
-.IR src_fd
+.I src_fd
 at offset
-.IR src_offset
+.I src_offset
 into the file
-.IR dest_fd
+.I dest_fd
 at offset
 .IR dest_offset ",
 provided that both are files.
 If
-.IR src_length
+.I src_length
 is zero, the ioctl reflinks to the end of the source file.
 This information is conveyed in a structure of
 the following form:
@@ -91,12 +91,12 @@ is set to indicate the error.
 Error codes can be one of, but are not limited to, the following:
 .TP
 .B EBADF
-.IR src_fd
+.I src_fd
 is not open for reading;
-.IR dest_fd
+.I dest_fd
 is not open for writing or is open for append-only writes;
 or the filesystem which
-.IR src_fd
+.I src_fd
 resides on does not support reflink.
 .TP
 .B EINVAL
@@ -117,7 +117,7 @@ This can appear if the filesystem does not support reflinking either file
 descriptor, or if either file descriptor refers to special inodes.
 .TP
 .B EPERM
-.IR dest_fd
+.I dest_fd
 is immutable.
 .TP
 .B ETXTBSY
diff --git a/man2/ioctl_fideduperange.2 b/man2/ioctl_fideduperange.2
index 84d20a276..20539f89d 100644
--- a/man2/ioctl_fideduperange.2
+++ b/man2/ioctl_fideduperange.2
@@ -49,9 +49,9 @@ being written.
 This behavior is commonly referred to as "copy on write".
 .PP
 This ioctl performs the "compare and share if identical" operation on up to
-.IR src_length
+.I src_length
 bytes from file descriptor
-.IR src_fd
+.I src_fd
 at offset
 .IR src_offset ".
 This information is conveyed in a structure of the following form:
@@ -95,48 +95,48 @@ struct file_dedupe_range_info {
 .in
 .PP
 Each deduplication operation targets
-.IR src_length
+.I src_length
 bytes in file descriptor
-.IR dest_fd
+.I dest_fd
 at offset
 .IR dest_offset ".
 The field
-.IR reserved
+.I reserved
 must be zero.
 During the call,
-.IR src_fd
+.I src_fd
 must be open for reading and
-.IR dest_fd
+.I dest_fd
 must be open for writing.
 The combined size of the struct
-.IR file_dedupe_range
+.I file_dedupe_range
 and the struct
-.IR file_dedupe_range_info
+.I file_dedupe_range_info
 array must not exceed the system page size.
 The maximum size of
-.IR src_length
+.I src_length
 is filesystem dependent and is typically 16\ MiB.
 This limit will be enforced silently by the filesystem.
 By convention, the storage used by
-.IR src_fd
+.I src_fd
 is mapped into
-.IR dest_fd
+.I dest_fd
 and the previous contents in
-.IR dest_fd
+.I dest_fd
 are freed.
 .PP
 Upon successful completion of this ioctl, the number of bytes successfully
 deduplicated is returned in
-.IR bytes_deduped
+.I bytes_deduped
 and a status code for the deduplication operation is returned in
 .IR status ".
 If even a single byte in the range does not match, the deduplication
 request will be ignored and
-.IR status
+.I status
 set to
 .BR FILE_DEDUPE_RANGE_DIFFERS .
 The
-.IR status
+.I status
 code is set to
 .B FILE_DEDUPE_RANGE_SAME
 for success, a negative error code in case of error, or
@@ -154,17 +154,17 @@ Error codes can be one of, but are not limited to, the following:
 .B ENOMEM
 The kernel was unable to allocate sufficient memory to perform the
 operation or
-.IR dest_count
+.I dest_count
 is so large that the input argument description spans more than a single
 page of memory.
 .TP
 .B EBADF
-.IR src_fd
+.I src_fd
 is not open for reading;
-.IR dest_fd
+.I dest_fd
 is not open for writing or is open for append-only writes; or the filesystem
 which
-.IR src_fd
+.I src_fd
 resides on does not support deduplication.
 .TP
 .B EINVAL
@@ -185,7 +185,7 @@ This can appear if the filesystem does not support deduplicating either file
 descriptor, or if either file descriptor refers to special inodes.
 .TP
 .B EPERM
-.IR dest_fd
+.I dest_fd
 is immutable.
 .TP
 .B ETXTBSY
diff --git a/man2/ioctl_getfsmap.2 b/man2/ioctl_getfsmap.2
index 6892946c5..1fb70874c 100644
--- a/man2/ioctl_getfsmap.2
+++ b/man2/ioctl_getfsmap.2
@@ -333,7 +333,7 @@ The error placed in
 can be one of, but is not limited to, the following:
 .TP
 .B EBADF
-.IR fd
+.I fd
 is not open for reading.
 .TP
 .B EBADMSG
diff --git a/man2/ioctl_iflags.2 b/man2/ioctl_iflags.2
index 9c77b08b9..871e6317e 100644
--- a/man2/ioctl_iflags.2
+++ b/man2/ioctl_iflags.2
@@ -118,7 +118,7 @@ This can provide I/O performance benefits for applications that do not care
 about the accuracy of this timestamp.
 This flag provides functionality similar to the
 .BR mount (2)
-.BR MS_NOATIME
+.B MS_NOATIME
 flag, but on a per-file basis.
 .\" .TP
 .\" .BR FS_NOCOMP_FL " \(aq\(aq"
@@ -161,10 +161,10 @@ is surprisingly difficult.
 Make file updates synchronous.
 For files, this makes all writes synchronous
 (as though all opens of the file were with the
-.BR O_SYNC
+.B O_SYNC
 flag).
 For directories, this has the same effect as the
-.BR FS_DIRSYNC_FL
+.B FS_DIRSYNC_FL
 flag.
 .TP
 .BR FS_TOPDIR_FL " \(aqT\(aq"
@@ -194,11 +194,11 @@ which is inherited only by subdirectories.
 Inode flags are a nonstandard Linux extension.
 .SH NOTES
 In order to change the inode flags of a file using the
-.BR FS_IOC_SETFLAGS
+.B FS_IOC_SETFLAGS
 operation,
 the effective user ID of the caller must match the owner of the file,
 or the caller must have the
-.BR CAP_FOWNER
+.B CAP_FOWNER
 capability.
 .SH SEE ALSO
 .BR chattr (1),
diff --git a/man2/ioctl_list.2 b/man2/ioctl_list.2
index 6683d0319..8729d2ee8 100644
--- a/man2/ioctl_list.2
+++ b/man2/ioctl_list.2
@@ -1010,7 +1010,7 @@ means
 after an N-byte pad.
 .I struct selection
 is implicitly defined in
-.IR drivers/char/selection.c
+.I drivers/char/selection.c
 .PP
 .nf
     TIOCLINUX-2         1 + const struct selection *
diff --git a/man2/ioctl_ns.2 b/man2/ioctl_ns.2
index 52fa4614f..cd7316ee6 100644
--- a/man2/ioctl_ns.2
+++ b/man2/ioctl_ns.2
@@ -47,7 +47,7 @@ new_fd = ioctl(fd, request);
 In each case,
 .I fd
 refers to a
-.IR /proc/[pid]/ns/*
+.I /proc/[pid]/ns/*
 file.
 Both operations return a new file descriptor on success.
 .TP
@@ -66,14 +66,14 @@ the namespace referred to by
 This operation is valid only for hierarchical namespaces
 (i.e., PID and user namespaces).
 For user namespaces,
-.BR NS_GET_PARENT
+.B NS_GET_PARENT
 is synonymous with
 .BR NS_GET_USERNS .
 .PP
 The new file descriptor returned by these operations is opened with the
-.BR O_RDONLY
+.B O_RDONLY
 and
-.BR O_CLOEXEC
+.B O_CLOEXEC
 (close-on-exec; see
 .BR fcntl (2))
 flags.
@@ -88,7 +88,7 @@ structure whose
 .I st_ino
 (inode number) fields together identify the owning/parent namespace.
 This inode number can be matched with the inode number of another
-.IR /proc/[pid]/ns/{pid,user}
+.I /proc/[pid]/ns/{pid,user}
 file to determine whether that is the owning/parent namespace.
 .PP
 Either of these
@@ -132,11 +132,11 @@ nstype = ioctl(fd, NS_GET_NSTYPE);
 .PP
 .I fd
 refers to a
-.IR /proc/[pid]/ns/*
+.I /proc/[pid]/ns/*
 file.
 .PP
 The return value is one of the
-.BR CLONE_NEW*
+.B CLONE_NEW*
 values that can be specified to
 .BR clone (2)
 or
@@ -162,7 +162,7 @@ ioctl(fd, NS_GET_OWNER_UID, &uid);
 .PP
 .I fd
 refers to a
-.IR /proc/[pid]/ns/user
+.I /proc/[pid]/ns/user
 file.
 .PP
 The owner user ID is returned in the
diff --git a/man2/ioctl_tty.2 b/man2/ioctl_tty.2
index 63cc14540..b98f681c3 100644
--- a/man2/ioctl_tty.2
+++ b/man2/ioctl_tty.2
@@ -91,7 +91,7 @@ Sets the locking status of the
 .I termios
 structure of the terminal.
 Only a process with the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
 capability can do this.
 .SS Get and set window size
 Window sizes are kept in the kernel, but not used by the kernel
@@ -224,7 +224,7 @@ If that was a pseudoterminal master, send it to the slave.
 In Linux before version 2.6.10,
 anybody can do this as long as the output was not redirected yet;
 since version 2.6.10, only a process with the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
 capability may do this.
 If output was redirected already
 .B EBUSY
@@ -249,7 +249,7 @@ If this terminal is already the controlling terminal
 of a different session group, then the ioctl fails with
 .BR EPERM ,
 unless the caller has the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
 capability and
 .I arg
 equals 1, in which case the terminal is stolen, and all processes that had
@@ -296,7 +296,7 @@ operations on the terminal are permitted.
 (They fail with
 .BR EBUSY ,
 except for a process with the
-.BR CAP_SYS_ADMIN
+.B CAP_SYS_ADMIN
 capability.)
 .TP
 .BI "TIOCGEXCL	int *" argp
@@ -368,9 +368,9 @@ Return the current packet mode setting in the integer pointed to by
 .TP
 .BI "TIOCSPTLCK	int *" argp
 Set (if
-.IR *argp
+.I *argp
 is nonzero) or remove (if
-.IR *argp
+.I *argp
 is zero) the pseudoterminal slave device.
 (See also
 .BR unlockpt (3).)
diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2
index 922b298ec..6df01eb54 100644
--- a/man2/ioctl_userfaultfd.2
+++ b/man2/ioctl_userfaultfd.2
@@ -60,17 +60,17 @@ The various
 .BR ioctl (2)
 operations are described below.
 The
-.BR UFFDIO_API,
+.BR UFFDIO_API ,
 .BR UFFDIO_REGISTER ,
 and
-.BR UFFDIO_UNREGISTER
+.B UFFDIO_UNREGISTER
 operations are used to
 .I configure
 userfaultfd behavior.
 These operations allow the caller to choose what features will be enabled and
 what kinds of events will be delivered to the application.
 The remaining operations are
-.IR range
+.I range
 operations.
 These operations enable the calling application to resolve page-fault
 events.
@@ -82,7 +82,7 @@ Enable operation of the userfaultfd and perform API handshake.
 The
 .I argp
 argument is a pointer to a
-.IR uffdio_api
+.I uffdio_api
 structure, defined as:
 .PP
 .in +4n
@@ -245,7 +245,7 @@ accessible address space.
 .TP
 .B EINVAL
 The userfaultfd has already been enabled by a previous
-.BR UFFDIO_API
+.B UFFDIO_API
 operation.
 .TP
 .B EINVAL
@@ -377,7 +377,7 @@ The pages in the range must be "compatible" (see the description of
 .BR  UFFDIO_REGISTER .)
 .PP
 The address range to unregister is specified in the
-.IR uffdio_range
+.I uffdio_range
 structure pointed to by
 .IR argp .
 .PP
@@ -431,7 +431,7 @@ struct uffdio_copy {
 .in
 .PP
 The following value may be bitwise ORed in
-.IR mode
+.I mode
 to change the behavior of the
 .B UFFDIO_COPY
 operation:
@@ -483,18 +483,18 @@ Either
 or
 .I len
 was not a multiple of the system page size, or the range specified by
-.IR src
+.I src
 and
-.IR len
+.I len
 or
-.IR dst
+.I dst
 and
-.IR len
+.I len
 was invalid.
 .TP
 .B EINVAL
 An invalid bit was specified in the
-.IR mode
+.I mode
 field.
 .TP
 .BR ENOENT " (since Linux 4.11)"
@@ -535,7 +535,7 @@ struct uffdio_zeropage {
 .in
 .PP
 The following value may be bitwise ORed in
-.IR mode
+.I mode
 to change the behavior of the
 .B UFFDIO_ZEROPAGE
 operation:
@@ -592,7 +592,7 @@ was zero; or the range specified was invalid.
 .TP
 .B EINVAL
 An invalid bit was specified in the
-.IR mode
+.I mode
 field.
 .TP
 .BR ESRCH " (since Linux 4.13)"
@@ -608,20 +608,20 @@ a specified memory address range.
 The
 .B UFFDIO_WAKE
 operation is used in conjunction with
-.BR UFFDIO_COPY
+.B UFFDIO_COPY
 and
-.BR UFFDIO_ZEROPAGE
+.B UFFDIO_ZEROPAGE
 operations that have the
-.BR UFFDIO_COPY_MODE_DONTWAKE
+.B UFFDIO_COPY_MODE_DONTWAKE
 or
-.BR UFFDIO_ZEROPAGE_MODE_DONTWAKE
+.B UFFDIO_ZEROPAGE_MODE_DONTWAKE
 bit set in the
 .I mode
 field.
 The userfault monitor can perform several
-.BR UFFDIO_COPY
+.B UFFDIO_COPY
 and
-.BR UFFDIO_ZEROPAGE
+.B UFFDIO_ZEROPAGE
 operations in a batch and then explicitly wake up the faulting thread using
 .BR UFFDIO_WAKE .
 .PP
@@ -664,7 +664,7 @@ does not point to a valid memory address.
 (For all operations except
 .BR UFFDIO_API .)
 The userfaultfd object has not yet been enabled (via the
-.BR UFFDIO_API
+.B UFFDIO_API
 operation).
 .SH CONFORMING TO
 These
@@ -674,10 +674,10 @@ operations are Linux-specific.
 In order to detect available userfault features and
 enable some subset of those features
 the userfaultfd file descriptor must be closed after the first
-.BR UFFDIO_API
+.B UFFDIO_API
 operation that queries features availability and reopened before
 the second
-.BR UFFDIO_API
+.B UFFDIO_API
 operation that actually enables the desired features.
 .SH EXAMPLE
 See
@@ -687,5 +687,5 @@ See
 .BR mmap (2),
 .BR userfaultfd (2)
 .PP
-.IR Documentation/admin-guide/mm/userfaultfd.rst
+.I Documentation/admin-guide/mm/userfaultfd.rst
 in the Linux kernel source tree
-- 
2.20.1


-- 
Bjarni I. Gislason



[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux