From: Alejandro Colomar <alx@kernel.org>
To: Seth McDonald <dev@sethm.id.au>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 4/5] man/man2/readv.2: HISTORY: ffix
Date: Sun, 22 Feb 2026 22:28:16 +0100 [thread overview]
Message-ID: <aZt0yjophKW3Jltt@devuan> (raw)
In-Reply-To: <f336517a9084b23f49da379a4d2a73f7a86c2e32.1771750388.git.dev@sethm.id.au>
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
On 2026-02-22T20:12:14+1000, Seth McDonald wrote:
> Signed-off-by: Seth McDonald <dev@sethm.id.au>
> ---
> man/man2/readv.2 | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/man/man2/readv.2 b/man/man2/readv.2
> index 765d487b9ff1..51549cf8214a 100644
> --- a/man/man2/readv.2
> +++ b/man/man2/readv.2
> @@ -462,13 +462,17 @@ .SH HISTORY
> .\" The readv/writev system calls were buggy before Linux 1.3.40.
> .\" (Says release.libc.)
> .P
> -.BR preadv (),
> -.BR pwritev ():
> +.TP
> +.BR preadv ()
> +.TQ
> +.BR pwritev ()
> Linux 2.6.30,
> glibc 2.10.
> .P
> -.BR preadv2 (),
> -.BR pwritev2 ():
> +.TP
> +.BR preadv2 ()
> +.TQ
> +.BR pwritev2 ()
> Linux 4.6,
> glibc 2.26.
> .SS Historical C library/kernel differences
This patch had issues:
remote: mandoc: .tmp/man/man2/readv.2:464:2: WARNING: skipping paragraph macro: PP empty
remote: mandoc: .tmp/man/man2/readv.2:471:2: WARNING: skipping paragraph macro: PP empty
remote: make: *** [/home/alx/src/linux/man-pages/man-pages/contrib/share/mk/lint/man/mandoc.mk:31: .tmp/man/man2/readv.2.lint-man.mandoc.touch] Error 1
So I amended it:
diff --git i/man/man2/readv.2 w/man/man2/readv.2
index 51549cf8214a..cbfc1e0ffa83 100644
--- i/man/man2/readv.2
+++ w/man/man2/readv.2
@@ -461,14 +461,12 @@ .SH HISTORY
.\" as the return type.
.\" The readv/writev system calls were buggy before Linux 1.3.40.
.\" (Says release.libc.)
-.P
.TP
.BR preadv ()
.TQ
.BR pwritev ()
Linux 2.6.30,
glibc 2.10.
-.P
.TP
.BR preadv2 ()
.TQ
> --
> 2.53.0.1
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-22 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 10:12 [PATCH 0/5] man/man2/*: Miscellaneous fixes Seth McDonald
2026-02-22 10:12 ` [PATCH 1/5] man/man2/open_tree.2: HISTORY: ffix Seth McDonald
2026-02-22 10:12 ` [PATCH 2/5] man/man2/perfmonctl.2: HISTORY: wfix Seth McDonald
2026-02-22 10:12 ` [PATCH 3/5] man/man2/process_madvise.2: HISTORY: ffix Seth McDonald
2026-02-22 10:12 ` [PATCH 4/5] man/man2/readv.2: " Seth McDonald
2026-02-22 21:28 ` Alejandro Colomar [this message]
2026-02-22 10:12 ` [PATCH 5/5] man/man2/s390_guarded_storage.2: " Seth McDonald
2026-02-22 21:20 ` [PATCH 0/5] man/man2/*: Miscellaneous fixes Alejandro Colomar
2026-02-22 21:26 ` Alejandro Colomar
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=aZt0yjophKW3Jltt@devuan \
--to=alx@kernel.org \
--cc=dev@sethm.id.au \
--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