Use a single-font-style macro (".B", ".I") for a single argument.
Remove unneeded quotation marks (").
The output from "nroff" and "groff" is unchanged, except for the
change "\fi" to "\fI" and adding the italic corrections in the file
"lirc.4".
Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
---
man4/initrd.4 | 28 ++++++++---------
man4/lirc.4 | 86 +++++++++++++++++++++++++--------------------------
man4/loop.4 | 6 ++--
3 files changed, 60 insertions(+), 60 deletions(-)
diff --git a/man4/initrd.4 b/man4/initrd.4
index ae5e38f64..6623080d8 100644
--- a/man4/initrd.4
+++ b/man4/initrd.4
@@ -57,7 +57,7 @@ chown root:disk /dev/initrd
.PP
Also, support for both "RAM disk" and "Initial RAM disk"
(e.g.,
-.BR CONFIG_BLK_DEV_RAM=y
+.B CONFIG_BLK_DEV_RAM=y
and
.BR CONFIG_BLK_DEV_INITRD=y )
must be compiled directly into the Linux kernel to use
@@ -117,7 +117,7 @@ root filesystem (e.g.,
then the kernel skips to the last step for the usual boot sequence.
.IP 5.
If the executable file
-.IR /linuxrc
+.I /linuxrc
is present in the initial root filesystem,
.I /linuxrc
is executed with UID 0.
@@ -145,16 +145,16 @@ If the normal root filesystem has a directory
the device
.I /dev/ram0
is moved from
-.IR /
+.I /
to
.IR /initrd .
Otherwise, if the directory
-.IR /initrd
+.I /initrd
does not exist, the device
.I /dev/ram0
is unmounted.
(When moved from
-.IR /
+.I /
to
.IR /initrd ,
.I /dev/ram0
@@ -164,7 +164,7 @@ If directory
.I /initrd
does not exist on the normal root filesystem
and any processes remain running from
-.IR /dev/ram0
+.I /dev/ram0
when
.I /linuxrc
exits, the behavior of the kernel is
@@ -249,9 +249,9 @@ For more information on NFS-mounted root see the kernel documentation file
.I Documentation/filesystems/nfsroot.txt
before Linux 2.6.33).
For more information on setting the root filesystem see also the
-.BR LILO
+.B LILO
and
-.BR LOADLIN
+.B LOADLIN
documentation.
.PP
It is also possible for the
@@ -260,7 +260,7 @@ executable to change the normal root device.
For
.I /linuxrc
to change the normal root device,
-.IR /proc
+.I /proc
must be mounted.
After mounting
.IR /proc ,
@@ -277,7 +277,7 @@ write the new root filesystem device number into
For an NFS root filesystem, the root device is changed by having
.I /linuxrc
write the NFS setting into files
-.IR /proc/sys/kernel/nfs-root-name
+.I /proc/sys/kernel/nfs-root-name
and
.I /proc/sys/kernel/nfs-root-addrs
and then writing 0xff (e.g., the pseudo-NFS-device number) into file
@@ -338,7 +338,7 @@ The loader program boots from floppy or other media with a minimal kernel
.IR /dev/ram ,
.IR /dev/initrd ,
and the ext2 filesystem) and loads
-.IR /dev/initrd
+.I /dev/initrd
with a gzipped version of the initial filesystem.
.IP 2.
The executable
@@ -360,7 +360,7 @@ creates and populates the root filesystem.
completed system yet.)
.IP 5.
The executable
-.IR /linuxrc
+.I /linuxrc
sets
.IR /proc/sys/kernel/real-root-dev ,
unmount
@@ -422,7 +422,7 @@ from CD-ROM without the need of any floppies.
The distribution could also use a
.B LILO
boot floppy and then bootstrap a bigger RAM disk via
-.IR /dev/initrd
+.I /dev/initrd
from the CD-ROM.
.\"
.\"
@@ -461,7 +461,7 @@ be fully unmounted if
.I /dev/ram0
is used by any process or has any filesystem mounted on it.
If
-.IR /dev/ram0
+.I /dev/ram0
is
.B not
fully unmounted, then
diff --git a/man4/lirc.4 b/man4/lirc.4
index fab6e4ea1..33d554544 100644
--- a/man4/lirc.4
+++ b/man4/lirc.4
@@ -37,7 +37,7 @@ depending on the underlying hardware.
Some hardware (typically TV-cards) decodes the IR signal internally
and provides decoded button presses as scancode values.
Drivers for this kind of hardware work in
-.BR LIRC_MODE_SCANCODE
+.B LIRC_MODE_SCANCODE
mode.
Such hardware usually does not support sending IR signals.
Furthermore, such hardware can only decode a limited set of IR protocols,
@@ -46,13 +46,13 @@ bundled with, for example, a TV-card.
.PP
Other hardware provides a stream of pulse/space durations.
Such drivers work in
-.BR LIRC_MODE_MODE2
+.B LIRC_MODE_MODE2
mode.
Sometimes, this kind of hardware also supports
sending IR data.
Such hardware can be used with (almost) any kind of remote.
This type of hardware can also be used in
-.BR LIRC_MODE_SCANCODE
+.B LIRC_MODE_SCANCODE
mode, in which case the kernel IR decoders will decode the IR.
These decoders can be written in extended BPF (see
.BR bpf (2))
@@ -72,18 +72,18 @@ provides 32-bit values representing a space or a pulse duration.
The time of the duration (microseconds) is encoded in the lower 24 bits.
The upper 8 bits indicate the type of package:
.TP 4
-.BR LIRC_MODE2_SPACE
+.B LIRC_MODE2_SPACE
Value reflects a space duration (microseconds).
.TP 4
-.BR LIRC_MODE2_PULSE
+.B LIRC_MODE2_PULSE
Value reflects a pulse duration (microseconds).
.TP 4
-.BR LIRC_MODE2_FREQUENCY
+.B LIRC_MODE2_FREQUENCY
Value reflects a frequency (Hz); see the
.B LIRC_SET_MEASURE_CARRIER_MODE
ioctl.
.TP 4
-.BR LIRC_MODE2_TIMEOUT
+.B LIRC_MODE2_TIMEOUT
Value reflects a space duration (microseconds).
The package reflects a timeout; see the
.B LIRC_SET_REC_TIMEOUT_REPORTS
@@ -132,9 +132,9 @@ The LIRC device's ioctl definition is bound by the ioctl function
definition of
.IR "struct file_operations" ,
leaving us with an
-.IR "unsigned int"
+.I unsigned int
for the ioctl command and an
-.IR "unsigned long"
+.I unsigned long
for the argument.
For the purposes of ioctl portability across 32-bit and 64-bit architectures,
these values are capped to their 32-bit sizes.
@@ -185,10 +185,10 @@ device has no receiver, this operation fails with the error
Otherwise, it returns the receive mode, which will be one of:
.RS
.TP
-.BR LIRC_MODE_MODE2
+.B LIRC_MODE_MODE2
The driver returns a sequence of pulse/space durations.
.TP
-.BR LIRC_MODE_SCANCODE
+.B LIRC_MODE_SCANCODE
The driver returns struct
.I lirc_scancode
values, each of which represents
@@ -197,9 +197,9 @@ a decoded button press.
.TP
.BR LIRC_SET_REC_MODE " (\fIint\fP)"
Set the receive mode.
-.IR val
+.I val
is either
-.BR LIRC_MODE_SCANCODE
+.B LIRC_MODE_SCANCODE
or
.BR LIRC_MODE_MODE2 .
If the
@@ -209,9 +209,9 @@ device has no receiver, this operation fails with the error
.TP
.BR LIRC_GET_SEND_MODE " (\fIvoid\fP)"
Return the send mode.
-.BR LIRC_MODE_PULSE
+.B LIRC_MODE_PULSE
or
-.BR LIRC_MODE_SCANCODE
+.B LIRC_MODE_SCANCODE
is supported.
If the
.B lirc
@@ -220,9 +220,9 @@ device cannot send, this operation fails with the error
.TP
.BR LIRC_SET_SEND_MODE " (\fIint\fP)"
Set the send mode.
-.IR val
+.I val
is either
-.BR LIRC_MODE_SCANCODE
+.B LIRC_MODE_SCANCODE
or
.BR LIRC_MODE_PULSE .
If the
@@ -256,16 +256,16 @@ return integer values with the minimum/maximum timeout that can be
set (microseconds).
Some devices have a fixed timeout.
For such drivers,
-.BR LIRC_GET_MIN_TIMEOUT
+.B LIRC_GET_MIN_TIMEOUT
and
-.BR LIRC_GET_MAX_TIMEOUT
+.B LIRC_GET_MAX_TIMEOUT
will fail with the error
.BR ENOTTY .
.TP
.BR LIRC_SET_REC_TIMEOUT " (\fIint\fP)"
Set the integer value for IR inactivity timeout (microseconds).
To be accepted, the value must be within the limits defined by
-.BR LIRC_GET_MIN_TIMEOUT
+.B LIRC_GET_MIN_TIMEOUT
and
.BR LIRC_GET_MAX_TIMEOUT .
A value of 0 (if supported by the hardware) disables all hardware
@@ -274,7 +274,7 @@ If the exact value cannot be set, then the next possible value
.I greater
than the given value should be set.
.TP
-.BR LIRC_GET_REC_TIMEOUT " (\fivoid\fP)"
+.BR LIRC_GET_REC_TIMEOUT " (\fI\,void\/\fP)"
Return the current inactivity timeout (microseconds).
Available since Linux 4.18.
.TP
@@ -313,9 +313,9 @@ See
.BR LIRC_SET_REC_CARRIER_RANGE " (\fIint\fP)"
Sets the lower bound of the receive carrier frequency (Hz).
For this to take affect, first set the lower bound using the
-.BR LIRC_SET_REC_CARRIER_RANGE
+.B LIRC_SET_REC_CARRIER_RANGE
ioctl, and then the upper bound using the
-.BR LIRC_SET_REC_CARRIER
+.B LIRC_SET_REC_CARRIER
ioctl.
.TP
.BR LIRC_SET_MEASURE_CARRIER_MODE " (\fIint\fP)"
@@ -325,7 +325,7 @@ is 1) or disable
.RI ( val
is 0) the measure mode.
If enabled, from the next key press on, the driver will send
-.BR LIRC_MODE2_FREQUENCY
+.B LIRC_MODE2_FREQUENCY
packets.
By default, this should be turned off.
.TP
@@ -365,72 +365,72 @@ will do nothing.
.SH FEATURES
.PP
the
-.BR LIRC_GET_FEATURES
+.B LIRC_GET_FEATURES
ioctl returns a bit mask describing features of the driver.
The following bits may be returned in the mask:
.TP
-.BR LIRC_CAN_REC_MODE2
+.B LIRC_CAN_REC_MODE2
The driver is capable of receiving using
.BR LIRC_MODE_MODE2 .
.TP
-.BR LIRC_CAN_REC_SCANCODE
+.B LIRC_CAN_REC_SCANCODE
The driver is capable of receiving using
.BR LIRC_MODE_SCANCODE .
.TP
-.BR LIRC_CAN_SET_SEND_CARRIER
+.B LIRC_CAN_SET_SEND_CARRIER
The driver supports changing the modulation frequency using
.BR LIRC_SET_SEND_CARRIER .
.TP
-.BR LIRC_CAN_SET_SEND_DUTY_CYCLE
+.B LIRC_CAN_SET_SEND_DUTY_CYCLE
The driver supports changing the duty cycle using
.BR LIRC_SET_SEND_DUTY_CYCLE .
.TP
-.BR LIRC_CAN_SET_TRANSMITTER_MASK
+.B LIRC_CAN_SET_TRANSMITTER_MASK
The driver supports changing the active transmitter(s) using
.BR LIRC_SET_TRANSMITTER_MASK .
.TP
-.BR LIRC_CAN_SET_REC_CARRIER
+.B LIRC_CAN_SET_REC_CARRIER
The driver supports setting the receive carrier frequency using
.BR LIRC_SET_REC_CARRIER .
Any
.B lirc
device since the drivers were merged in kernel release 2.6.36
must have
-.BR LIRC_CAN_SET_REC_CARRIER_RANGE
+.B LIRC_CAN_SET_REC_CARRIER_RANGE
set if
-.BR LIRC_CAN_SET_REC_CARRIER
+.B LIRC_CAN_SET_REC_CARRIER
feature is set.
.TP
-.BR LIRC_CAN_SET_REC_CARRIER_RANGE
+.B LIRC_CAN_SET_REC_CARRIER_RANGE
The driver supports
.BR LIRC_SET_REC_CARRIER_RANGE .
The lower bound of the carrier must first be set using the
-.BR LIRC_SET_REC_CARRIER_RANGE
+.B LIRC_SET_REC_CARRIER_RANGE
ioctl, before using the
-.BR LIRC_SET_REC_CARRIER
+.B LIRC_SET_REC_CARRIER
ioctl to set the upper bound.
.TP
-.BR LIRC_CAN_GET_REC_RESOLUTION
+.B LIRC_CAN_GET_REC_RESOLUTION
The driver supports
.BR LIRC_GET_REC_RESOLUTION .
.TP
-.BR LIRC_CAN_SET_REC_TIMEOUT
+.B LIRC_CAN_SET_REC_TIMEOUT
The driver supports
.BR LIRC_SET_REC_TIMEOUT .
.TP
-.BR LIRC_CAN_MEASURE_CARRIER
+.B LIRC_CAN_MEASURE_CARRIER
The driver supports measuring of the modulation frequency using
.BR LIRC_SET_MEASURE_CARRIER_MODE .
.TP
-.BR LIRC_CAN_USE_WIDEBAND_RECEIVER
+.B LIRC_CAN_USE_WIDEBAND_RECEIVER
The driver supports learning mode using
.BR LIRC_SET_WIDEBAND_RECEIVER .
.TP
-.BR LIRC_CAN_SEND_PULSE
+.B LIRC_CAN_SEND_PULSE
The driver supports sending using
-.BR LIRC_MODE_PULSE
+.B LIRC_MODE_PULSE
or
-.BR LIRC_MODE_SCANCODE
+.B LIRC_MODE_SCANCODE
.\"
.SH BUGS
Using these devices requires the kernel source header file
diff --git a/man4/loop.4 b/man4/loop.4
index 6b3460262..d4f079192 100644
--- a/man4/loop.4
+++ b/man4/loop.4
@@ -119,7 +119,7 @@ The
field is a bit mask that can include zero or more of the following:
.RS
.TP
-.BR LO_FLAGS_READ_ONLY
+.B LO_FLAGS_READ_ONLY
The loopback device is read-only.
.TP
.BR LO_FLAGS_AUTOCLEAR " (since Linux 2.6.25)"
@@ -192,7 +192,7 @@ the kernel provides the
device, which permits an application to dynamically find a free device,
and to add and remove loop devices from the system.
To perform these operations, one first opens
-.IR /dev/loop-control
+.I /dev/loop-control
and then employs one of the following
.BR ioctl (2)
operations:
@@ -221,7 +221,7 @@ If the device is in use, the call fails with the error
.BR EBUSY .
.SH FILES
.TP
-.IR /dev/loop*
+.I /dev/loop*
The loop block special device files.
.SH EXAMPLE
The program below uses the
--
2.20.1
