From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Omar Sandoval <osandov@osandov.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>
Cc: mtk.manpages@gmail.com, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [PATCH v2] fideduperange.2: fix the discussion of maximum sizes
Date: Wed, 23 Nov 2016 08:06:46 +0100 [thread overview]
Message-ID: <5ad80a74-15c6-548c-3de9-757a5ae77de9@gmail.com> (raw)
In-Reply-To: <20161123044941.GB27107@mew>
On 11/23/2016 05:49 AM, Omar Sandoval wrote:
> On Tue, Nov 22, 2016 at 08:48:16PM -0800, Darrick J. Wong wrote:
>> Fix the discussion of the limitations on the dest_count and src_length
>> parameters to the fideduperange ioctl to reflect what's actually in the
>> kernel.
>>
>> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
>> ---
>> man2/ioctl_fideduperange.2 | 20 +++++++++++++++++---
>> 1 file changed, 17 insertions(+), 3 deletions(-)
>>
>> diff --git a/man2/ioctl_fideduperange.2 b/man2/ioctl_fideduperange.2
>> index 2112d10..057229d 100644
>> --- a/man2/ioctl_fideduperange.2
>> +++ b/man2/ioctl_fideduperange.2
[...]
> Reviewed-by: Omar Sandoval <osandov@fb.com>
Thanks Omar!
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2016-11-23 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 4:48 [PATCH v2] fideduperange.2: fix the discussion of maximum sizes Darrick J. Wong
2016-11-23 4:49 ` Omar Sandoval
2016-11-23 7:06 ` Michael Kerrisk (man-pages) [this message]
2016-11-23 7:05 ` 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=5ad80a74-15c6-548c-3de9-757a5ae77de9@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=osandov@osandov.com \
/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).