From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: Linux Man-Pages <linux-man@vger.kernel.org>
Cc: Alejandro Colomar <alx.manpages@gmail.com>
Subject: [PATCH 08/11] man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs
Date: Sun, 5 Feb 2023 16:58:52 -0700 [thread overview]
Message-ID: <20230205235855.64261-4-Brian.Inglis@Shaw.ca> (raw)
In-Reply-To: <20230205235855.64261-1-Brian.Inglis@Shaw.ca>
[-- Attachment #1: Type: text/plain, Size: 89 bytes --]
---
man2/adjtimex.2 | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0008-man2-adjtimex.2-use-ISO-IEC-suffixes-and-digit-separ.patch --]
[-- Type: text/x-patch; name="0008-man2-adjtimex.2-use-ISO-IEC-suffixes-and-digit-separ.patch", Size: 1570 bytes --]
diff --git a/man2/adjtimex.2 b/man2/adjtimex.2
index df7d27cd4e5e..fe613672cd93 100644
--- a/man2/adjtimex.2
+++ b/man2/adjtimex.2
@@ -108,7 +108,7 @@ Set frequency offset from
.IR buf.freq .
Since Linux 2.6.26,
.\" commit 074b3b87941c99bc0ce35385b5817924b1ed0c23
-the supplied value is clamped to the range (\-32768000, +32768000).
+the supplied value is clamped to the range (\-32\[aq]000Ki, +32\[aq]000Ki).
In older kernels, an
.B EINVAL
error occurs if the supplied value is out of range.
@@ -471,7 +471,7 @@ does not point to writable memory.
.BR EINVAL " (before Linux 2.6.26)"
An attempt was made to set
.I buf.freq
-to a value outside the range (\-33554432, +33554432).
+to a value outside the range (\-32Mi, +32Mi).
.\" From a quick glance, it appears there was no clamping or range check
.\" for buf.freq before Linux 2.0
.TP
@@ -479,8 +479,8 @@ to a value outside the range (\-33554432, +33554432).
An attempt was made to set
.I buf.offset
to a value outside the permitted range.
-Before Linux 2.0, the permitted range was (\-131072, +131072).
-From Linux 2.0 onwards, the permitted range was (\-512000, +512000).
+Before Linux 2.0, the permitted range was (\-128Ki, +128Ki).
+From Linux 2.0 onwards, the permitted range was (\-512k, +512k).
.TP
.B EINVAL
An attempt was made to set
@@ -505,9 +505,9 @@ for a discussion of dynamic clocks.
An attempt was made to set
.I buf.tick
to a value outside the range
-.RB 900000/ HZ
+.RB 900k/ HZ
to
-.RB 1100000/ HZ ,
+.RB 1\[aq]100k/ HZ ,
where
.B HZ
is the system timer interrupt frequency.
next prev parent reply other threads:[~2023-02-05 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 23:58 [PATCH 05/11] man2/reboot.2: show BCD dates in hex not decimal Brian Inglis
2023-02-05 23:58 ` [PATCH 06/11] man2/reboot.2: punctuate hex in docs with digit separators Brian Inglis
2023-02-05 23:58 ` [PATCH 07/11] man2/statfs.2: " Brian Inglis
2023-02-05 23:58 ` Brian Inglis [this message]
2023-02-05 23:58 ` [PATCH 09/11] man2/getrandom.2: change limit to use IEC suffix Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 20:32 [PATCH 00/11] man2/: punctuate long numeric strings with digit separators Brian Inglis
2023-02-07 20:32 ` [PATCH 08/11] man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230205235855.64261-4-Brian.Inglis@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox