Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Aug 2015 11:56:20 +0000 (UTC)
From:      Christian Brueffer <brueffer@FreeBSD.org>
To:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   svn commit: r286663 - in head/share/man: man4 man4/man4.i386 man7 man8 man9
Message-ID:  <201508121156.t7CBuK6k005425@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: brueffer
Date: Wed Aug 12 11:56:19 2015
New Revision: 286663
URL: https://svnweb.freebsd.org/changeset/base/286663

Log:
  Fix mandoc warnings/errors.
  
  MFC after:	1 week

Modified:
  head/share/man/man4/cloudabi.4
  head/share/man/man4/ctl.4
  head/share/man/man4/em.4
  head/share/man/man4/gre.4
  head/share/man/man4/hptiop.4
  head/share/man/man4/man4.i386/wl.4
  head/share/man/man4/ng_btsocket.4
  head/share/man/man4/siftr.4
  head/share/man/man4/snp.4
  head/share/man/man4/uftdi.4
  head/share/man/man4/vt.4
  head/share/man/man7/release.7
  head/share/man/man8/nanobsd.8
  head/share/man/man8/uefi.8
  head/share/man/man8/yp.8
  head/share/man/man9/PCI_IOV_ADD_VF.9
  head/share/man/man9/PCI_IOV_INIT.9
  head/share/man/man9/altq.9
  head/share/man/man9/ifnet.9

Modified: head/share/man/man4/cloudabi.4
==============================================================================
--- head/share/man/man4/cloudabi.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/cloudabi.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -99,5 +99,4 @@ cloudlibc on GitHub:
 CloudABI support first appeared in
 .Fx 11.0 .
 .Sh AUTHORS
-Nuxi:
-.Pa https://nuxi.nl/ .
+.An Nuxi : Pa https://nuxi.nl/ .

Modified: head/share/man/man4/ctl.4
==============================================================================
--- head/share/man/man4/ctl.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/ctl.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -119,6 +119,7 @@ In the event that there is no response w
 forcibly terminated.
 Set to 0 to disable sending NOP-In PDUs.
 Defaults to 5.
+.El
 .Sh SEE ALSO
 .Xr ctladm 8 ,
 .Xr ctld 8 ,

Modified: head/share/man/man4/em.4
==============================================================================
--- head/share/man/man4/em.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/em.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -307,5 +307,4 @@ The
 driver was written by
 .An Intel Corporation Aq Mt freebsd@intel.com .
 .Sh BUGS
-.Pp
 Activating EM_MULTIQUEUE support requires MSI-X features.

Modified: head/share/man/man4/gre.4
==============================================================================
--- head/share/man/man4/gre.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/gre.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -154,7 +154,6 @@ ifconfig greN create
 ifconfig greN inet 198.51.100.1 203.0.113.1
 ifconfig greN inet tunnel 198.51.100.1 203.0.113.1 tunnelfib 1
 .Ed
-.Pp
 .Sh NOTES
 The MTU of
 .Nm

Modified: head/share/man/man4/hptiop.4
==============================================================================
--- head/share/man/man4/hptiop.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/hptiop.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -135,4 +135,5 @@ device driver first appeared in
 .Sh AUTHORS
 The
 .Nm
-driver was written by HighPoint Technologies, Inc.
+driver was written by
+.An HighPoint Technologies, Inc.

Modified: head/share/man/man4/man4.i386/wl.4
==============================================================================
--- head/share/man/man4/man4.i386/wl.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/man4.i386/wl.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -165,7 +165,9 @@ ported the Mach drivers to BSDI.
 ported them to
 .Fx 2.1 .
 .An Michael Smith
-ported the wl driver only to 2.2.2.
+ported the
+.Nm
+driver only to 2.2.2.
 Jim and Michael have been
 maintaining them.
 The current state of the driver is NOT ANYONE'S

Modified: head/share/man/man4/ng_btsocket.4
==============================================================================
--- head/share/man/man4/ng_btsocket.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/ng_btsocket.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -45,8 +45,8 @@ module implements three Netgraph node ty
 Each type in its turn implements one protocol within
 .Dv PF_BLUETOOTH
 domain.
-.Sh Dv BLUETOOTH_PROTO_HCI Sh protocol
-.Ss Dv SOCK_RAW Ss HCI sockets
+.Sh Dv BLUETOOTH_PROTO_HCI protocol
+.Ss Dv SOCK_RAW HCI sockets
 Implemented by
 .Nm btsock_hci_raw
 Netgraph type.
@@ -147,7 +147,7 @@ level can be used to obtain via
 or change via
 .Xr setsockopt 2
 raw HCI socket's filter.
-.Sh Dv BLUETOOTH_PROTO_L2CAP Sh protocol
+.Sh Dv BLUETOOTH_PROTO_L2CAP protocol
 The Bluetooth L2CAP socket address is defined as follows:
 .Bd -literal -offset indent
 /* Bluetooth version of struct sockaddr for L2CAP sockets */
@@ -158,7 +158,7 @@ struct sockaddr_l2cap {
         bdaddr_t  l2cap_bdaddr; /* address */
 };
 .Ed
-.Ss Dv SOCK_RAW Ss L2CAP sockets
+.Ss Dv SOCK_RAW L2CAP sockets
 Implemented by
 .Nm btsock_l2c_raw
 Netgraph type.
@@ -204,7 +204,7 @@ The
 variable, that can be examined and set via
 .Xr sysctl 8 ,
 controls the control request timeout (in seconds) for raw L2CAP sockets.
-.Ss Dv SOCK_SEQPACKET Ss L2CAP sockets
+.Ss Dv SOCK_SEQPACKET L2CAP sockets
 Implemented by
 .Nm btsock_l2c
 Netgraph type.
@@ -264,7 +264,7 @@ Get (set) value of the flush timeout.
 Not implemented.
 .Ef
 .El
-.Sh Dv BLUETOOTH_PROTO_RFCOMM Sh protocol
+.Sh Dv BLUETOOTH_PROTO_RFCOMM protocol
 The Bluetooth RFCOMM socket address is defined as follows:
 .Bd -literal -offset indent
 /* Bluetooth version of struct sockaddr for RFCOMM sockets */
@@ -275,7 +275,7 @@ struct sockaddr_rfcomm {
         uint8_t  rfcomm_channel; /* channel */
 };
 .Ed
-.Ss Dv SOCK_STREAM Ss RFCOMM sockets
+.Ss Dv SOCK_STREAM RFCOMM sockets
 Note that RFCOMM sockets do not have associated Netgraph node type.
 RFCOMM sockets are implemented as additional layer on top of L2CAP sockets.
 RFCOMM sockets are either

Modified: head/share/man/man4/siftr.4
==============================================================================
--- head/share/man/man4/siftr.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/siftr.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -345,7 +345,7 @@ network interface card and drivers being
 .Bl -tag -offset indent -width Va
 .It Va 28
 Flow type for the connection.
-Flowtype defines which protocol fields are hashed to produce the flowid. 
+Flowtype defines which protocol fields are hashed to produce the flowid.
 A complete listing is available in
 .Pa sys/mbuf.h
 under

Modified: head/share/man/man4/snp.4
==============================================================================
--- head/share/man/man4/snp.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/snp.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -85,7 +85,7 @@ driver was rewritten to work with the re
 .Sh AUTHORS
 .An -nosplit
 The author of the current implementation is
-.An Ed Schouten Aq Mt ed@FreeBSD.org .
+.An \&Ed Schouten Aq Mt ed@FreeBSD.org .
 Previous versions of
 .Nm
 were based on code written by

Modified: head/share/man/man4/uftdi.4
==============================================================================
--- head/share/man/man4/uftdi.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/uftdi.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -193,7 +193,7 @@ struct uftdi_eeio
 .Pp
 The FT232R chip has an internal eeprom.
 An external serial eeprom is optional on other FTDI chips.
-The eeprom may contain 64, 128, or 256 words, 
+The eeprom may contain 64, 128, or 256 words,
 depending on the part used.
 Multiple calls may be needed to read or write the larger parts.
 When no eeprom is present, all words in the returned data are 0xffff.

Modified: head/share/man/man4/vt.4
==============================================================================
--- head/share/man/man4/vt.4	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man4/vt.4	Wed Aug 12 11:56:19 2015	(r286663)
@@ -327,8 +327,8 @@ driver first appeared in
 The
 .Nm
 device driver was developed by
-.An Ed Schouten Aq Mt ed@FreeBSD.org ,
-.An Ed Maste Aq Mt emaste@FreeBSD.org ,
+.An \&Ed Schouten Aq Mt ed@FreeBSD.org ,
+.An \&Ed Maste Aq Mt emaste@FreeBSD.org ,
 and
 .An Aleksandr Rybalko Aq Mt ray@FreeBSD.org ,
 with sponsorship provided by the

Modified: head/share/man/man7/release.7
==============================================================================
--- head/share/man/man7/release.7	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man7/release.7	Wed Aug 12 11:56:19 2015	(r286663)
@@ -435,7 +435,6 @@ include support for each hosting provide
 The following
 .Xr make 1
 environment variables are supported:
-.Pp
 .Bl -tag -width Ev
 .It Va CLOUDWARE
 Set to a list of one or more cloud hosting providers, enclosed in quotes.

Modified: head/share/man/man8/nanobsd.8
==============================================================================
--- head/share/man/man8/nanobsd.8	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man8/nanobsd.8	Wed Aug 12 11:56:19 2015	(r286663)
@@ -104,7 +104,7 @@ Making use of just one shell script and 
 possible to build reduced and customized images satisfying any arbitrary
 set of requirements.
 .El
-.Ss Nm NanoBSD Ss Media Layout
+.Ss NanoBSD Media Layout
 The mass storage medium is divided into three parts by default (which
 are normally mounted read-only):
 .Pp

Modified: head/share/man/man8/uefi.8
==============================================================================
--- head/share/man/man8/uefi.8	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man8/uefi.8	Wed Aug 12 11:56:19 2015	(r286663)
@@ -114,7 +114,7 @@ typical non-default kernel (optional)
 .Xr vt 4 ,
 .Xr msdosfs 5 ,
 .Xr boot 8 ,
-.Xr gpart 8 , 
+.Xr gpart 8 ,
 .Xr uefisign 8
 .Sh HISTORY
 .Nm
@@ -125,7 +125,7 @@ boot support first appeared in
 .Nm
 boot support was developed by
 .An Benno Rice Aq Mt benno@FreeBSD.org ,
-.An Ed Maste Aq Mt emaste@FreeBSD.org ,
+.An \&Ed Maste Aq Mt emaste@FreeBSD.org ,
 and
 .An Nathan Whitehorn Aq Mt nwhitehorn@FreeBSD.org .
 The

Modified: head/share/man/man8/yp.8
==============================================================================
--- head/share/man/man8/yp.8	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man8/yp.8	Wed Aug 12 11:56:19 2015	(r286663)
@@ -464,9 +464,11 @@ Some systems, such as
 .Tn NIS
 to be running in order
 for their hostname resolution functions
-.Fn ( gethostbyname ,
+.Po Fn gethostbyname ,
 .Fn gethostbyaddr ,
-etc.) to work properly.
+etc.
+.Pc
+to work properly.
 On these systems,
 .Xr ypserv 8
 performs
@@ -499,13 +501,14 @@ It can also be made to register itself a
 v1 server
 in order to placate certain systems that insist on the presence of
 a v1 server
-.No ( Fx
+.Po Fx
 uses only
 .Tn NIS
 v2, but many other systems,
 including
 .Tn SunOS
-4.x, search for both a v1 and v2 server when binding).
+4.x, search for both a v1 and v2 server when binding
+.Pc .
 .Fx Ns 's
 .Xr ypserv 8
 does not actually handle

Modified: head/share/man/man9/PCI_IOV_ADD_VF.9
==============================================================================
--- head/share/man/man9/PCI_IOV_ADD_VF.9	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man9/PCI_IOV_ADD_VF.9	Wed Aug 12 11:56:19 2015	(r286663)
@@ -104,8 +104,8 @@ the PF.
 .Sh SEE ALSO
 .Xr nv 9 ,
 .Xr pci 9 ,
-.Xr pci_iov_schema 9 ,
 .Xr PCI_IOV_INIT 9 ,
+.Xr pci_iov_schema 9 ,
 .Xr PCI_IOV_UNINIT 9
 .Sh AUTHORS
 This manual page was written by

Modified: head/share/man/man9/PCI_IOV_INIT.9
==============================================================================
--- head/share/man/man9/PCI_IOV_INIT.9	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man9/PCI_IOV_INIT.9	Wed Aug 12 11:56:19 2015	(r286663)
@@ -77,8 +77,8 @@ and no VFs will be created.
 .Sh SEE ALSO
 .Xr nv 9 ,
 .Xr pci 9 ,
-.Xr pci_iov_schema 9 ,
 .Xr PCI_IOV_ADD_VF 9 ,
+.Xr pci_iov_schema 9 ,
 .Xr PCI_IOV_UNINIT 9
 .Sh AUTHORS
 This manual page was written by

Modified: head/share/man/man9/altq.9
==============================================================================
--- head/share/man/man9/altq.9	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man9/altq.9	Wed Aug 12 11:56:19 2015	(r286663)
@@ -237,7 +237,7 @@ sets a flag to indicate that a driver wa
 .Nm
 can be enabled only on interfaces with this flag.
 .Sh COMPATIBILITY
-.Ss Vt ifaltq Ss structure
+.Ss Vt ifaltq structure
 In order to keep compatibility with the existing code, the new
 output queue structure
 .Vt ifaltq

Modified: head/share/man/man9/ifnet.9
==============================================================================
--- head/share/man/man9/ifnet.9	Wed Aug 12 11:30:31 2015	(r286662)
+++ head/share/man/man9/ifnet.9	Wed Aug 12 11:56:19 2015	(r286663)
@@ -215,7 +215,7 @@ Interfaces are also associated with an o
 this structure is used to hold packets while the interface is in the
 process of sending another.
 .Pp
-.Ss The Vt ifnet Ss structure
+.Ss The ifnet Structure
 The fields of
 .Vt "struct ifnet"
 are as follows:
@@ -840,7 +840,7 @@ routine.
 The
 .Xr polling
 handler returns the number of packets processed.
-.Ss The Vt if_data Ss Structure
+.Ss The if_data Structure
 The
 .Vt if_data
 structure contains statistics and identifying information used
@@ -1021,7 +1021,7 @@ The link is down.
 .It Dv LINK_STATE_UP
 The link is up.
 .El
-.Ss The Vt ifaddr Ss Structure
+.Ss The ifaddr Structure
 Every interface is associated with a list
 (or, rather, a
 .Li TAILQ )
@@ -1119,7 +1119,7 @@ In addition to these functions, there
 may also be link-layer support routines which are used by a number of
 drivers implementing a specific link layer over different hardware;
 see the documentation for that link layer for more details.
-.Ss The Vt ifmultiaddr Ss Structure
+.Ss The ifmultiaddr Structure
 Every multicast-capable interface is associated with a list of
 multicast group memberships, which indicate at a low level which
 link-layer multicast addresses (if any) should be accepted, and at a



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201508121156.t7CBuK6k005425>