Remove EOL whitespace.

Found with:	mandoc -Tlint

share/man/man4/altera_atse.4

@@ -80,7 +80,7 @@ Only a single MAC address may be stored in flash.
 If the address begins with the Altera prefix 00:07:ed and ends in 00 then
 up to 16 addresses will be derived from it by adding the unit number of
 the interface to the stored address.
-For other prefixes, the address will be assigned to atse0 and random     
+For other prefixes, the address will be assigned to atse0 and random
 addresses will be used for other interfaces.
 If the stored address is invalid, for example all zero's, multicast, or the
 default address shipped on all DE4 boards (00:07:ed:ff:ed:15) then a random

share/man/man4/gpioled.4

@@ -52,8 +52,8 @@ The GPIO pin can then be controlled by writing to this device as described
 in
 .Xr led 4 .
 .Pp
-On a 
-.Xr device.hints 5 
+On a
+.Xr device.hints 5
 based system, like
 .Li MIPS ,
 these values are configurable for

share/man/man4/iicbus.4

@@ -106,11 +106,11 @@ Some I2C interfaces are available:
 .Sh BUS FREQUENCY CONFIGURATION
 The operating frequency of an I2C bus may be fixed or configurable.
 The bus may be used as part of some larger standard interface, and that
-interface specification may require a fixed frequency.  
-The driver for that hardware would not honor an attempt to configure a 
+interface specification may require a fixed frequency.
+The driver for that hardware would not honor an attempt to configure a
 different speed.
 A general purpose I2C bus, such as those found in many embedded systems,
-will often support multiple bus frequencies.  
+will often support multiple bus frequencies.
 .Pp
 When a system supports multiple I2C busses, a different frequency can
 be configured for each bus by number, represented by the
@@ -145,7 +145,7 @@ The same variable can be changed at any time with
 Reset the bus using
 .Xr i2c 8
 or the
-.Xr iic 4 
+.Xr iic 4
 .Va I2CRSTCARD
 ioctl to make the change take effect.
 .Sh SEE ALSO

share/man/man4/iscsi_initiator.4

@@ -47,7 +47,7 @@ iscsi_initiator_load="YES"
 .Sh DESCRIPTION
 .Bf -symbolic
 This driver, along with its userspace counterpart
-.Xr iscontrol 8 , 
+.Xr iscontrol 8 ,
 is obsolete.
 Users are advised to use
 .Xr iscsi 4

share/man/man4/mpr.4

@@ -59,7 +59,7 @@ mpr_load="YES"
 .Ed
 .Sh DESCRIPTION
 The
-.Nm 
+.Nm
 driver provides support for LSI Fusion-MPT 3 IT/IR
 .Tn SAS
 controllers.

share/man/man4/mrsas.4

@@ -27,7 +27,7 @@
 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
 .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
-.\" 
+.\"
 .\" The views and conclusions contained in the software and documentation
 .\" are those of the authors and should not be interpreted as representing
 .\" official policies, either expressed or implied, of the FreeBSD Project.
@@ -57,15 +57,15 @@ mrsas_load="YES"
 .Ed
 .Sh DESCRIPTION
 The
-.Nm 
+.Nm
 driver will detect LSI's next generation (6Gb/s and 12Gb/s) PCI Express
 SAS/SATA RAID controllers.
 See the
 .Nm HARDWARE
 section for the supported devices list.
-A disk (virtual disk/physical disk) attached to the 
+A disk (virtual disk/physical disk) attached to the
 .Nm
-driver will be visible to the user through 
+driver will be visible to the user through
 .Xr camcontrol 8
 as
 .Pa /dev/da?
@@ -79,11 +79,11 @@ The
 name is derived from the phrase "MegaRAID SAS HBA", which is
 substantially different than the old "MegaRAID" Driver
 .Xr mfi 4
-which does not connect targets 
-to the 
+which does not connect targets
+to the
+.Xr cam 4
+layer and thus requires a new driver which attaches targets to the
 .Xr cam 4
-layer and thus requires a new driver which attaches targets to the 
-.Xr cam 4 
 layer.
 Older MegaRAID controllers are supported by
 .Xr mfi 4
@@ -91,7 +91,7 @@ and will not work with
 .Nm ,
 but both the
 .Xr mfi 4
-and 
+and
 .Nm
 drivers can detect and manage the LSI MegaRAID SAS 2208/2308/3008/3108 series of
 controllers.
@@ -104,8 +104,8 @@ driver's behavior for LSI MegaRAID SAS 2208/2308/3008/3108 controllers.
 By default, the
 .Xr mfi 4
 driver will detect these controllers.
-See the 
-.Nm PRIORITY 
+See the
+.Nm PRIORITY
 section to know more about driver priority for MR-Fusion devices.
 .Pp
 .Nm
@@ -164,16 +164,16 @@ DELL PERC H330
 .Sh CONFIGURATION
 To disable Online Controller Reset(OCR) for a specific
 .Nm
-driver instance, set the 
+driver instance, set the
 following tunable value in
 .Xr loader.conf 5 :
 .Bd -literal -offset indent
-dev.mrsas.X.disable_ocr=1 
+dev.mrsas.X.disable_ocr=1
 .Ed
 .Pp
 where X is the adapter number.
 .Pp
-To change the I/O timeout value for a specific 
+To change the I/O timeout value for a specific
 .Nm
 driver instance, set the following tunable value in
 .Xr loader.conf 5 :
@@ -230,12 +230,12 @@ and
 .Dv BUS_PROBE_LOW_PRIORITY ) .
 MR-Fusion Controllers include all cards with the
 Device IDs -
-0x005B, 
+0x005B,
 0x005D,
 0x005F.
 .Pp
 The
-.Xr mfi 4 
+.Xr mfi 4
 driver will set a priority of either
 .Dv BUS_PROBE_DEFAULT
 or
@@ -254,13 +254,13 @@ for the
 .Nm
 driver to detect a MR-Fusion card instead of the
 .Xr mfi 4
-driver. 
+driver.
 .Bd -ragged -offset indent
 .Cd hw.mfi.mrsas_enable="1"
 .Ed
 .Pp
 At boot time, the
-.Xr mfi 4 
+.Xr mfi 4
 driver will get priority to detect MR-Fusion controllers by default.
 Before
 changing this default driver selection policy, LSI advises users to understand
@@ -273,9 +273,9 @@ driver to detect MR-Fusion cards, but allow for the ability to choose the
 driver to detect MR-Fusion cards.
 .Pp
 LSI recommends setting hw.mfi.mrsas_enable="0" for customers who are using the
-older 
-.Xr mfi 4 
-driver and do not want to switch to 
+older
+.Xr mfi 4
+driver and do not want to switch to
 .Nm .
 For those customers who are using a MR-Fusion controller for the first time, LSI
 recommends using the
@@ -286,8 +286,8 @@ Changing the default behavior is well tested under most conditions, but
 unexpected behavior may pop up if more complex and unrealistic operations are
 executed by switching between the
 .Xr mfi 4
-and 
-.Nm 
+and
+.Nm
 drivers for MR-Fusion.
 Switching drivers is designed to happen only one time.
 Although multiple
@@ -296,16 +296,16 @@ The user should decide from
 .Nm Start of Day
 which driver they want to use for the MR-Fusion card.
 .Pp
-The user may see different device names when switching from 
-.Xr mfi 4 
-to 
+The user may see different device names when switching from
+.Xr mfi 4
+to
 .Nm .
 This behavior is
 .Nm Functions As Designed
 and the user needs to change the
 .Xr fstab 5
-entry manually if they are doing any experiments with 
-.Xr mfi 4 
+entry manually if they are doing any experiments with
+.Xr mfi 4
 and
 .Nm
 interoperability.
@@ -342,7 +342,7 @@ is the new driver reworked by LSI which supports Thunderbolt and onward
 products.
 The SAS+SATA RAID controller with device id 0x005b is referred to as
 the Thunderbolt controller throughout this man page.
-.Ed 
+.Ed
 .Bd -ragged
 .Nm cam aware HBA drivers:
 .Fx
@@ -351,12 +351,12 @@ has a
 layer which attaches storage devices and provides a common access mechanism to
 storage controllers and attached devices.
 The
-.Nm 
+.Nm
 driver is
 .Xr cam 4
-aware and devices associated with 
-.Nm 
-can be seen using 
+aware and devices associated with
+.Nm
+can be seen using
 .Xr camcontrol 8 .
 The
 .Xr mfi 4
@@ -364,13 +364,13 @@ driver does not understand the
 .Xr cam 4
 layer and it directly associates storage disks to the block layer.
 .Pp
-.Nm Thunderbolt Controller: 
+.Nm Thunderbolt Controller:
 This is the 6Gb/s MegaRAID HBA card which has device id 0x005B.
 .Pp
-.Nm Invader Controller: 
+.Nm Invader Controller:
 This is 12Gb/s MegaRAID HBA card which has device id 0x005D.
 .Pp
-.Nm Fury Controller: 
+.Nm Fury Controller:
 This is the 12Gb/s MegaRAID HBA card which has device id 0x005F.
 .Ed
 .Sh AUTHORS
@@ -387,11 +387,11 @@ switches between two drivers and does not want to edit
 manually).
 .Pp
 The
-.Nm 
+.Nm
 driver exposes devices as
 .Pa /dev/da? ,
-whereas 
-.Xr mfi 4 
+whereas
+.Xr mfi 4
 exposes devices as
 .Pa /dev/mfid? .
 .Pp

share/man/man4/netmap.4

@@ -143,7 +143,7 @@ but can be independently configured to share memory.
 .Sh ENTERING AND EXITING NETMAP MODE
 The following section describes the system calls to create
 and control
-.Nm netmap 
+.Nm netmap
 ports (including
 .Nm VALE
 and

share/man/man4/tap.4

@@ -34,7 +34,7 @@ or a terminal for
 and a character-special device
 .Dq control
 interface.
-A client program transfers Ethernet frames to or from the 
+A client program transfers Ethernet frames to or from the
 .Nm
 .Dq control
 interface.

share/man/man4/tun.4

@@ -35,7 +35,7 @@ or a terminal for
 and a character-special device
 .Dq control
 interface.
-A client program transfers IP (by default) packets to or from the 
+A client program transfers IP (by default) packets to or from the
 .Nm
 .Dq control
 interface.

share/man/man4/umass.4

@@ -62,7 +62,7 @@ or
 .Xr ohci 4
 or
 .Xr ehci 4
-or 
+or
 .Xr xhci 4
 must be configured in the kernel.
 Additionally, since

share/man/man4/wsp.4

@@ -52,7 +52,7 @@ device found in many Apple laptops.
 .Pp
 The driver simulates a three-button mouse using multi-finger tap
 detection.
-A single-finger press generates a left button click. 
+A single-finger press generates a left button click.
 A two-finger tap maps to the right button; whereas a three-finger tap
 gets treated as a middle button click.
 .Pp