All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Michael Kerrisk
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH] wait.2: Add paragraph break before errno note in RETURN VALUE section.
Date: Wed, 24 Sep 2014 11:55:37 -0400	[thread overview]
Message-ID: <5422E979.8030606@redhat.com> (raw)

The text "Each of these calls sets errno to an appropriate
value in the case of an error." is not only for waitid.

This patch adds a paragraph break to move the errno note
to a new paragraph where it makes sense, as it applies to
all the wait* functions.

Tested against upstream master.

diff --git a/man2/wait.2 b/man2/wait.2
index 224055f..4d5fc77 100644
--- a/man2/wait.2
+++ b/man2/wait.2
@@ -378,6 +378,7 @@ on error, \-1 is returned.
 .\" returns the PID of the child.  Either this is a bug, or it is intended
 .\" behavior that needs to be documented.  See my Jan 2009 LKML mail
 .\" "waitid() return value strangeness when infop is NULL".
+.PP
 Each of these calls sets
 .I errno
 to an appropriate value in the case of an error.
---

Cheers,
Carlos.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-09-24 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 15:55 Carlos O'Donell [this message]
     [not found] ` <5422E979.8030606-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-09-25 10:20   ` [PATCH] wait.2: Add paragraph break before errno note in RETURN VALUE section 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=5422E979.8030606@redhat.com \
    --to=carlos-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.