From: Simon Paillard <spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] umount.2: Homogeneous wording, don't recall function name
Date: Sat, 1 Mar 2014 03:42:59 +0100 [thread overview]
Message-ID: <20140301024259.GL19183@mraw.org> (raw)
In-Reply-To: <1393630618-11940-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Hi,
On Sat, Mar 01, 2014 at 12:36:58AM +0100, Simon Paillard wrote:
> See:
> man2/link.2:An invalid flag value was specified in
> man2/swapon.2:An invalid flag value was specified in
> man2/umount.2:An invalid flag value was specified in
> man2/unlink.2:An invalid flag value was specified in
Forget this patch, as umount manpage explains both umount() and umount2(),
hence the need to explicit which function EINVAL details are about.
> ---
> man2/umount.2 | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/man2/umount.2 b/man2/umount.2
> index 86fff50..18a87a0 100644
> --- a/man2/umount.2
> +++ b/man2/umount.2
> @@ -137,8 +137,7 @@ or
> .BR MNT_FORCE .
> .TP
> .BR EINVAL " (since Linux 2.6.34)"
> -.BR umount2 ()
> -was called with an invalid flag value in
> +An invalid flag value was specified in
> .IR flags .
> .TP
> .B ENAMETOOLONG
> --
> 1.8.5.3
--
Simon Paillard
--
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
next prev parent reply other threads:[~2014-03-01 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 23:36 [PATCH] umount.2: Homogeneous wording, don't recall function name Simon Paillard
[not found] ` <1393630618-11940-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-03-01 2:42 ` Simon Paillard [this message]
[not found] ` <20140301024259.GL19183-xazfMhTT2R0@public.gmane.org>
2014-03-03 4:49 ` 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=20140301024259.GL19183@mraw.org \
--to=spaillard-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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.