From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Simon Paillard <spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH 1/2] fallocate.2: 0 is returned on *success*
Date: Wed, 12 Jun 2013 15:10:05 +0200 [thread overview]
Message-ID: <51B8732D.3020703@gmail.com> (raw)
In-Reply-To: <1370980770-25405-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
On 06/11/13 21:59, Simon Paillard wrote:
> Introduced by 47a979088fcd7f
> ---
> man2/fallocate.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/fallocate.2 b/man2/fallocate.2
> index a61c513..58a19c2 100644
> --- a/man2/fallocate.2
> +++ b/man2/fallocate.2
> @@ -110,7 +110,7 @@ Not all file systems support
> .BR FALLOC_FL_PUNCH_HOLE ;
> if a file system doesn't support the operation, an error is returned.
> .SH RETURN VALUE
> -On error,
> +On success,
> .BR fallocate ()
> returns zero.
> On error, \-1 is returned and
Hi Simon,
I recently fixed this after a report from Yuri Kozlov.
Cheers,
Michael
--
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
prev parent reply other threads:[~2013-06-12 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 19:59 [PATCH 1/2] fallocate.2: 0 is returned on *success* Simon Paillard
[not found] ` <1370980770-25405-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-06-11 19:59 ` [PATCH 2/2] siginterrupt.3: tfix missing dot Simon Paillard
[not found] ` <1370980770-25405-2-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-06-12 13:10 ` Michael Kerrisk
2013-06-12 13:10 ` Michael Kerrisk [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=51B8732D.3020703@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spaillard-8fiUuRrzOP0dnm+yROfE0A@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.