Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Jan 2016 13:33:22 +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: r293421 - head/share/man/man9
Message-ID:  <201601081333.u08DXMjk047441@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: brueffer
Date: Fri Jan  8 13:33:22 2016
New Revision: 293421
URL: https://svnweb.freebsd.org/changeset/base/293421

Log:
  Fix issues found by mandoc -Tlint.
  
  MFC after:	1 week

Modified:
  head/share/man/man9/DEVICE_PROBE.9
  head/share/man/man9/kern_testfrwk.9
  head/share/man/man9/malloc.9
  head/share/man/man9/timeout.9

Modified: head/share/man/man9/DEVICE_PROBE.9
==============================================================================
--- head/share/man/man9/DEVICE_PROBE.9	Fri Jan  8 10:35:57 2016	(r293420)
+++ head/share/man/man9/DEVICE_PROBE.9	Fri Jan  8 13:33:22 2016	(r293421)
@@ -100,7 +100,8 @@ This is for source or binary drivers tha
 tree.
 Its use in the base OS is prohibited.
 .It BUS_PROBE_DEFAULT
-The device is a normal device matching some plug and play ID.  This is
+The device is a normal device matching some plug and play ID.
+This is
 the normal return value for drivers to use.
 It is intended that nearly all of the drivers in the tree should return
 this value.

Modified: head/share/man/man9/kern_testfrwk.9
==============================================================================
--- head/share/man/man9/kern_testfrwk.9	Fri Jan  8 10:35:57 2016	(r293420)
+++ head/share/man/man9/kern_testfrwk.9	Fri Jan  8 13:33:22 2016	(r293421)
@@ -65,7 +65,6 @@ When your test loads, you register your 
 You do that through a call to
 .Fn kern_testframework_register .
 Usually this is done at the module load event as shown below:
-.Pp
 .Bd -literal -offset indent
 	switch (type) {
 	case MOD_LOAD:
@@ -122,7 +121,6 @@ field is a test-specific set of informat
 It is passed in from user space and has a maximum size of 256 bytes.
 You can pass arbitrary test input in the space.
 In the case of callout_test we reshape that to:
-.Pp
 .Bd -literal -offset indent
 struct callout_test {
 	int number_of_callouts;
@@ -133,7 +131,6 @@ struct callout_test {
 So the first lines of
 .Fn run_callout_test
 does the following to get at the user specific data:
-.Pp
 .\" This is a bad example and violates strict aliasing.  It should be replaced.
 .Bd -literal -offset indent
 	struct callout_test *u;

Modified: head/share/man/man9/malloc.9
==============================================================================
--- head/share/man/man9/malloc.9	Fri Jan  8 10:35:57 2016	(r293420)
+++ head/share/man/man9/malloc.9	Fri Jan  8 13:33:22 2016	(r293421)
@@ -229,7 +229,7 @@ may sleep when called with
 never sleeps.
 However,
 .Fn malloc ,
-.Fn realloc,
+.Fn realloc ,
 .Fn reallocf
 and
 .Fn free

Modified: head/share/man/man9/timeout.9
==============================================================================
--- head/share/man/man9/timeout.9	Fri Jan  8 10:35:57 2016	(r293420)
+++ head/share/man/man9/timeout.9	Fri Jan  8 13:33:22 2016	(r293421)
@@ -261,7 +261,7 @@ returns zero it will arrange for the fun
 .Fa drain
 to be called using the same argument given to the
 .Fn callout_reset
-function. 
+function.
 .Fn callout_async_drain
 If the callout has an associated lock,
 then that lock must be held when this function is called.



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