Use a single-font-change macro for a single argument. The output from "nroff" and "groff" is unchanged. Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx> --- man2/s390_guarded_storage.2 | 4 ++-- man2/s390_pci_mmio_write.2 | 14 +++++++------- man2/s390_runtime_instr.2 | 10 +++++----- man2/s390_sthyi.2 | 4 ++-- man2/sched_get_priority_max.2 | 2 +- man2/sched_rr_get_interval.2 | 2 +- man2/sched_setaffinity.2 | 4 ++-- man2/sched_setattr.2 | 32 ++++++++++++++++---------------- man2/sched_setscheduler.2 | 16 ++++++++-------- man2/sched_yield.2 | 4 ++-- 10 files changed, 46 insertions(+), 46 deletions(-) diff --git a/man2/s390_guarded_storage.2 b/man2/s390_guarded_storage.2 index fee842e1a..24fea9804 100644 --- a/man2/s390_guarded_storage.2 +++ b/man2/s390_guarded_storage.2 @@ -108,14 +108,14 @@ On success, the return value of is 0. .PP On error, \-1 is returned, and -.IR errno +.I errno is set appropriately. .SH ERRORS .TP .B EFAULT .I command was -.BR GS_SET_BC_CB +.B GS_SET_BC_CB and the copying of the guarded storage control block structure pointed by the .I gs_cb argument has failed. diff --git a/man2/s390_pci_mmio_write.2 b/man2/s390_pci_mmio_write.2 index c6ec89892..f76e6c0e7 100644 --- a/man2/s390_pci_mmio_write.2 +++ b/man2/s390_pci_mmio_write.2 @@ -39,9 +39,9 @@ MMIO memory page The .BR s390_pci_mmio_write () system call writes -.IR length +.I length bytes of data from the user-space buffer -.IR user_buffer +.I user_buffer to the PCI MMIO memory location specified by .IR mmio_addr . The @@ -50,7 +50,7 @@ system call reads .I length bytes of data from the PCI MMIO memory location specified by -.IR mmio_addr +.I mmio_addr to the user-space buffer .IR user_buffer . .PP @@ -58,11 +58,11 @@ These system calls must be used instead of the simple assignment or data-transfer operations that are used to access the PCI MMIO memory areas mapped to user space on the Linux System z platform. The address specified by -.IR mmio_addr +.I mmio_addr must belong to a PCI MMIO memory page mapping in the caller's address space, and the data being written or read must not cross a page boundary. The -.IR length +.I length value cannot be greater than the system page size. .SH RETURN VALUE On success, @@ -71,7 +71,7 @@ and .BR s390_pci_mmio_read () return 0. On error, \-1 is returned and -.IR errno +.I errno is set to one of the error codes listed below. .SH ERRORS .TP @@ -81,7 +81,7 @@ The address in is invalid. .TP .B EFAULT -.IR user_buffer +.I user_buffer does not point to a valid location in the caller's address space. .TP .B EINVAL diff --git a/man2/s390_runtime_instr.2 b/man2/s390_runtime_instr.2 index 17613148a..8afebad18 100644 --- a/man2/s390_runtime_instr.2 +++ b/man2/s390_runtime_instr.2 @@ -38,7 +38,7 @@ system call starts or stops CPU run-time instrumentation for the calling thread. .PP The -.IR command +.I command argument controls whether run-time instrumentation is started .RB ( S390_RUNTIME_INSTR_START , 1) or stopped @@ -46,7 +46,7 @@ argument controls whether run-time instrumentation is started 2) for the calling thread. .PP The -.IR signum +.I signum argument specifies the number of a real-time signal. The real-time signal is sent to the thread if the run-time instrumentation buffer is full or if the run-time-instrumentation-halted interrupt @@ -60,15 +60,15 @@ instrumentation control block. The caller can then read and modify the control block and start the run-time instrumentation. On error, \-1 is returned and -.IR errno +.I errno is set to one of the error codes listed below. .SH ERRORS .TP .B EINVAL The value specified in -.IR command +.I command is not a valid command or the value specified in -.IR signum +.I signum is not a real-time signal number. .TP .B ENOMEM diff --git a/man2/s390_sthyi.2 b/man2/s390_sthyi.2 index 01b1013bc..007148436 100644 --- a/man2/s390_sthyi.2 +++ b/man2/s390_sthyi.2 @@ -90,12 +90,12 @@ in the range [0..3]. A return value of 0 indicates that CPU capacity information is stored in .IR *resp_buffer . A return value of 3 indicates "unsupported function code" and the content of -.IR *resp_buffer +.I *resp_buffer is unchanged. The return values 1 and 2 are reserved. .PP On error, \-1 is returned, and -.IR errno +.I errno is set appropriately. .SH ERRORS .TP diff --git a/man2/sched_get_priority_max.2 b/man2/sched_get_priority_max.2 index a22fc5969..c8ff58741 100644 --- a/man2/sched_get_priority_max.2 +++ b/man2/sched_get_priority_max.2 @@ -79,7 +79,7 @@ thus it is a good idea for portable applications to use a virtual priority range and map it to the interval given by .BR sched_get_priority_max () and -.BR sched_get_priority_min +.B sched_get_priority_min POSIX.1 requires .\" POSIX.1-2001, POSIX.1-2008 (XBD 2.8.4) a spread of at least 32 between the maximum and the minimum values for diff --git a/man2/sched_rr_get_interval.2 b/man2/sched_rr_get_interval.2 index 04f0725be..14668135d 100644 --- a/man2/sched_rr_get_interval.2 +++ b/man2/sched_rr_get_interval.2 @@ -118,7 +118,7 @@ starting with Linux 2.6.24. Linux 3.9 added .\" commit ce0dbbbb30aee6a835511d5be446462388ba9eee a new mechanism for adjusting (and viewing) the -.BR SCHED_RR +.B SCHED_RR quantum: the .I /proc/sys/kernel/sched_rr_timeslice_ms file exposes the quantum as a millisecond value, whose default is 100. diff --git a/man2/sched_setaffinity.2 b/man2/sched_setaffinity.2 index 7d4096437..b4f19d874 100644 --- a/man2/sched_setaffinity.2 +++ b/man2/sched_setaffinity.2 @@ -181,9 +181,9 @@ available on the system, including: inspecting the contents of using .BR sysconf (3) to obtain the values of the -.BR _SC_NPROCESSORS_CONF +.B _SC_NPROCESSORS_CONF and -.BR _SC_NPROCESSORS_ONLN +.B _SC_NPROCESSORS_ONLN parameters; and inspecting the list of CPU directories under .IR /sys/devices/system/cpu/ . .PP diff --git a/man2/sched_setattr.2 b/man2/sched_setattr.2 index 492ccbcf7..952bb1bb9 100644 --- a/man2/sched_setattr.2 +++ b/man2/sched_setattr.2 @@ -54,15 +54,15 @@ Currently, Linux supports the following "normal" (i.e., non-real-time) scheduling policies as values that may be specified in .IR policy : .TP 14 -.BR SCHED_OTHER +.B SCHED_OTHER the standard round-robin time-sharing policy; .\" In the 2.6 kernel sources, SCHED_OTHER is actually called .\" SCHED_NORMAL. .TP -.BR SCHED_BATCH +.B SCHED_BATCH for "batch" style execution of processes; and .TP -.BR SCHED_IDLE +.B SCHED_IDLE for running .I very low priority background jobs. @@ -73,13 +73,13 @@ the way in which runnable threads are selected for execution. For the rules governing when a process may use these policies, see .BR sched (7). The real-time policies that may be specified in -.IR policy +.I policy are: .TP 14 -.BR SCHED_FIFO +.B SCHED_FIFO a first-in, first-out policy; and .TP -.BR SCHED_RR +.B SCHED_RR a round-robin policy. .PP Linux also provides the following policy: @@ -125,7 +125,7 @@ the kernel verifies that all additional fields are 0; if they are not, .BR sched_setattr () fails with the error -.BR E2BIG +.B E2BIG and updates .I size to contain the size of the kernel structure. @@ -146,7 +146,7 @@ that does not support the larger structure. .TP .I sched_policy This field specifies the scheduling policy, as one of the -.BR SCHED_* +.B SCHED_* values listed above. .TP .I sched_flags @@ -162,9 +162,9 @@ for details. .TP .I sched_nice This field specifies the nice value to be set when specifying -.IR sched_policy +.I sched_policy as -.BR SCHED_OTHER +.B SCHED_OTHER or .BR SCHED_BATCH . The nice value is a number in the range \-20 (high priority) @@ -173,9 +173,9 @@ to +19 (low priority); see .TP .I sched_priority This field specifies the static priority to be set when specifying -.IR sched_policy +.I sched_policy as -.BR SCHED_FIFO +.B SCHED_FIFO or .BR SCHED_RR . The allowed range of priorities for these policies can be determined using @@ -189,7 +189,7 @@ This field specifies the "Runtime" parameter for deadline scheduling. The value is expressed in nanoseconds. This field, and the next two fields, are used only for -.BR SCHED_DEADLINE +.B SCHED_DEADLINE scheduling; for further details, see .BR sched (7). .TP @@ -332,7 +332,7 @@ or is invalid; or .I attr.sched_policy is -.BR SCHED_DEADLINE +.B SCHED_DEADLINE and the deadline scheduling parameters in .I attr are invalid. @@ -373,9 +373,9 @@ In Linux versions up to 3.15, .BR sched_settattr () failed with the error -.BR EFAULT +.B EFAULT instead of -.BR E2BIG +.B E2BIG for the case described in ERRORS. .\" In Linux versions up to up 3.15, .\" FIXME . patch from Peter Zijlstra pending diff --git a/man2/sched_setscheduler.2 b/man2/sched_setscheduler.2 index fde20825f..a29ce8cea 100644 --- a/man2/sched_setscheduler.2 +++ b/man2/sched_setscheduler.2 @@ -69,21 +69,21 @@ Currently, Linux supports the following "normal" (i.e., non-real-time) scheduling policies as values that may be specified in .IR policy : .TP 14 -.BR SCHED_OTHER +.B SCHED_OTHER the standard round-robin time-sharing policy; .\" In the 2.6 kernel sources, SCHED_OTHER is actually called .\" SCHED_NORMAL. .TP -.BR SCHED_BATCH +.B SCHED_BATCH for "batch" style execution of processes; and .TP -.BR SCHED_IDLE +.B SCHED_IDLE for running .I very low priority background jobs. .PP For each of the above policies, -.IR param\->sched_priority +.I param\->sched_priority must be 0. .PP Various "real-time" policies are also supported, @@ -92,17 +92,17 @@ the way in which runnable threads are selected for execution. For the rules governing when a process may use these policies, see .BR sched (7). The real-time policies that may be specified in -.IR policy +.I policy are: .TP 14 -.BR SCHED_FIFO +.B SCHED_FIFO a first-in, first-out policy; and .TP -.BR SCHED_RR +.B SCHED_RR a round-robin policy. .PP For each of the above policies, -.IR param\->sched_priority +.I param\->sched_priority specifies a scheduling priority for the thread. This is a number in the range returned by calling .BR sched_get_priority_min (2) diff --git a/man2/sched_yield.2 b/man2/sched_yield.2 index 92dd1c52b..3d28de32a 100644 --- a/man2/sched_yield.2 +++ b/man2/sched_yield.2 @@ -79,13 +79,13 @@ which will degrade system performance. .PP .BR sched_yield () is intended for use with real-time scheduling policies (i.e., -.BR SCHED_FIFO +.B SCHED_FIFO or .BR SCHED_RR ). Use of .BR sched_yield () with nondeterministic scheduling policies such as -.BR SCHED_OTHER +.B SCHED_OTHER is unspecified and very likely means your application design is broken. .SH SEE ALSO .BR sched (7) -- 2.20.1
