linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Rasmus Villemoes <rv@rasmusvillemoes.dk>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] errno.3: add some comments on EAGAIN/EWOULDBLOCK and EDEADLK/EDEADLOCK
Date: Sun, 1 Sep 2019 16:47:02 +0200	[thread overview]
Message-ID: <663e645a-0397-2589-6085-449fa0d3682b@gmail.com> (raw)
In-Reply-To: <20190829100621.11386-1-rv@rasmusvillemoes.dk>

Hello Rasmus,

On 8/29/19 12:06 PM, Rasmus Villemoes wrote:
> Signed-off-by: Rasmus Villemoes <rv@rasmusvillemoes.dk>
> ---
>  man3/errno.3 | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)

Thanks. I applied and tweaked a little.

Thanks,

Michael

> diff --git a/man3/errno.3 b/man3/errno.3
> index 6cbbafed5..794be7c7b 100644
> --- a/man3/errno.3
> +++ b/man3/errno.3
> @@ -94,7 +94,7 @@ must have distinct values, with the exception of
>  .B EAGAIN
>  and
>  .BR EWOULDBLOCK ,
> -which may be the same.
> +which may be the same. On Linux, these two always have the same value.
>  .PP
>  The error numbers that correspond to each symbolic name
>  vary across UNIX systems,
> @@ -240,8 +240,9 @@ Connection reset (POSIX.1-2001).
>  Resource deadlock avoided (POSIX.1-2001).
>  .TP
>  .B EDEADLOCK
> -Synonym for
> +On most platforms, a synonym for
>  .BR EDEADLK .
> +On some (e.g. Linux mips, powerpc, sparc), it is a separate error code "File locking deadlock error".
>  .TP
>  .B EDESTADDRREQ
>  Destination address required (POSIX.1-2001).
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2019-09-01 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 10:06 [PATCH] errno.3: add some comments on EAGAIN/EWOULDBLOCK and EDEADLK/EDEADLOCK Rasmus Villemoes
2019-09-01 14:47 ` Michael Kerrisk (man-pages) [this message]

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=663e645a-0397-2589-6085-449fa0d3682b@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=rv@rasmusvillemoes.dk \
    /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).