Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
	linux-man@vger.kernel.org, Mark Kettenis <kettenis@openbsd.org>
Subject: [PATCH v2] errno.3: ENODATA is an XSI STREAMS extension
Date: Sat, 20 Mar 2021 12:42:04 +0100	[thread overview]
Message-ID: <20210320114203.2329-1-alx.manpages@gmail.com> (raw)
In-Reply-To: <4db92b50-d9f9-f1b5-13dd-54a525e561df@gmail.com>

Reported-by: Mark Kettenis <kettenis@openbsd.org>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
 man3/errno.3 | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/man3/errno.3 b/man3/errno.3
index fe9b7f715..48e3e63f3 100644
--- a/man3/errno.3
+++ b/man3/errno.3
@@ -403,7 +403,8 @@ No buffer space available (POSIX.1 (XSI STREAMS option)).
 .\" ENOCSI is defined but appears to be unused.
 .TP
 .B ENODATA
-No message is available on the STREAM head read queue (POSIX.1-2001).
+No message is available on the STREAM head read queue
+(POSIX.1-2001 (XSI STREAMS option)).
 .TP
 .B ENODEV
 No such device (POSIX.1-2001).
-- 
2.30.1


  reply	other threads:[~2021-03-20 11:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 23:57 [PATCH] errno.3: ENODATA is an XSI STREAMS extension Alejandro Colomar
2021-03-20  9:58 ` Jakub Wilk
2021-03-20 11:41   ` Alejandro Colomar (man-pages)
2021-03-20 11:42     ` Alejandro Colomar [this message]
2021-03-20 19:08       ` [PATCH v2] " Florian Weimer
2021-03-20 19:31         ` Alejandro Colomar (man-pages)
2021-03-20 19:41           ` Florian Weimer
2021-03-20 20:01             ` [PATCH v3] errno.3: Fix ENODATA text Alejandro Colomar
2021-04-04 20:16               ` Michael Kerrisk (man-pages)
2021-04-04 20:17                 ` 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=20210320114203.2329-1-alx.manpages@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=kettenis@openbsd.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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