From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Torin Carey <torin@tcarey.uk>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] unix.7: tfix
Date: Thu, 31 Oct 2019 06:19:12 +0100 [thread overview]
Message-ID: <cabdb001-2089-c5aa-36c6-7d4040681e47@gmail.com> (raw)
In-Reply-To: <20191029125142.GA17313@kappa>
Thanks again, Torin. Patch applied.
Cheers,
Michael
On 10/29/19 1:51 PM, Torin Carey wrote:
> In the given example, the second recvmsg(2) call should receive four bytes,
> as the third sendmsg(2) call only sends four.
> ---
> man7/unix.7 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man7/unix.7 b/man7/unix.7
> index a9d54c8c0..bdd5091d1 100644
> --- a/man7/unix.7
> +++ b/man7/unix.7
> @@ -566,7 +566,7 @@ The first call will receive five bytes of data,
> along with the ancillary data sent by the second
> .BR sendmsg (2)
> call.
> -The next call will receive the remaining five bytes of data.
> +The next call will receive the remaining four bytes of data.
> .PP
> If the space allocated for receiving incoming ancillary data is too small
> then the ancillary data is truncated to the number of headers
>
next prev parent reply other threads:[~2019-10-31 5:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 12:51 [PATCH] unix.7: tfix Torin Carey
2019-10-31 5:19 ` Michael Kerrisk (man-pages) [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-27 21:38 Štěpán Němec
2021-07-28 20:32 ` Alejandro Colomar (man-pages)
2019-10-29 12:41 Torin Carey
2019-10-31 5:18 ` Michael Kerrisk (man-pages)
2012-05-05 20:01 David Prévot
[not found] ` <1336248062-19460-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-05-05 21:35 ` Michael Kerrisk (man-pages)
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=cabdb001-2089-c5aa-36c6-7d4040681e47@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=torin@tcarey.uk \
/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;
as well as URLs for NNTP newsgroup(s).