Fix range upper bound for uint32_t and uint64_t, and reformat range

description for uint8_t, uint16_t, uint32_t, and uint64_t.

Differential Revision: https://reviews.freebsd.org/D2988
Reviewed by: rstone, wblock
Approved by: jmallett (mentor)
Sponsored by: Norse Corp, Inc.
This commit is contained in:
Patrick Kelsey 2015-07-06 01:48:23 +00:00
parent 4959a176f8
commit 2ccda62ff8
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=285189

View File

@ -25,7 +25,7 @@
.\"
.\" $FreeBSD$
.\"
.Dd May 21, 2014
.Dd July 5, 2015
.Dt IOVCTL.CONF 5
.Os
.Sh NAME
@ -103,13 +103,17 @@ xx:xx:xx:xx:xx:xx, where xx is one or two hexadecimal digits.
.It string
Accepts any string value.
.It uint8_t
Accepts any integer in the range 0-255, inclusive.
Accepts any integer in the range 0 to 255, inclusive.
.It uint16_t
Accepts any integer in the range 0-65535, inclusive.
Accepts any integer in the range 0 to 65535, inclusive.
.It uint32_t
Accepts any integer in the range 0-2**32, inclusive.
Accepts any integer in the range 0 to
.Po 2**32 - 1 Pc ,
inclusive.
.It uint64_t
Accepts any integer in the range 0-2**64, inclusive.
Accepts any integer in the range 0 to
.Po 2**64 - 1 Pc ,
inclusive.
.El
.Sh OPTIONS
The following parameters are accepted by all PF drivers: