From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: mtk.manpages@gmail.com, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [PATCH] ioctl_ficlonerange.2: mention a subtlety with length == 0
Date: Sat, 16 Jul 2016 12:26:01 +0200 [thread overview]
Message-ID: <9c68078c-0723-7a8a-bee9-484bfd1ebdc7@gmail.com> (raw)
In-Reply-To: <20160714181111.GC5215@birch.djwong.org>
On 07/14/2016 08:11 PM, Darrick J. Wong wrote:
> I forgot to document that passing length == 0 to clonerange actually
> makes it clone all the way to EOF, so do that now.
Thanks, Darrick. Applied.
Cheers,
Michael
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> man2/ioctl_ficlonerange.2 | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/man2/ioctl_ficlonerange.2 b/man2/ioctl_ficlonerange.2
> index d1da3e6..c4715d0 100644
> --- a/man2/ioctl_ficlonerange.2
> +++ b/man2/ioctl_ficlonerange.2
> @@ -59,6 +59,9 @@ into the file
> at offset
> .IR dest_offset ",
> provided that both are files.
> +If
> +.IR src_length
> +is zero, the ioctl reflinks to the end of the source file.
> This information is conveyed in a structure of
> the following form:
> .in +4n
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2016-07-16 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 18:11 [PATCH] ioctl_ficlonerange.2: mention a subtlety with length == 0 Darrick J. Wong
2016-07-16 10:26 ` 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=9c68078c-0723-7a8a-bee9-484bfd1ebdc7@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.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 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).