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 09/11] man2/getrandom.2: change limit to use IEC suffix
Date: Sun, 5 Feb 2023 16:58:53 -0700 [thread overview]
Message-ID: <20230205235855.64261-5-Brian.Inglis@Shaw.ca> (raw)
In-Reply-To: <20230205235855.64261-1-Brian.Inglis@Shaw.ca>
[-- Attachment #1: Type: text/plain, Size: 77 bytes --]
---
man2/getrandom.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0009-man2-getrandom.2-change-limit-to-use-IEC-suffix.patch --]
[-- Type: text/x-patch; name="0009-man2-getrandom.2-change-limit-to-use-IEC-suffix.patch", Size: 427 bytes --]
diff --git a/man2/getrandom.2 b/man2/getrandom.2
index e66815450b9c..24c0c0b80a6e 100644
--- a/man2/getrandom.2
+++ b/man2/getrandom.2
@@ -188,7 +188,7 @@ As of Linux 3.19 the following limits apply:
.IP \(bu 3
When reading from the
.I urandom
-source, a maximum of 33554431 bytes is returned by a single call to
+source, a maximum of 32Mi-1 bytes is returned by a single call to
.BR getrandom ()
on systems where
.I int
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 ` [PATCH 08/11] man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs Brian Inglis
2023-02-05 23:58 ` Brian Inglis [this message]
-- 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 09/11] man2/getrandom.2: change limit to use IEC suffix 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-5-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