linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: mtk.manpages@gmail.com, linux-api@vger.kernel.org,
	linux-man@vger.kernel.org, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] ioctl_getfsmap.2: correct semantics of FMR_OF_LAST flag
Date: Thu, 24 Aug 2017 00:33:48 +0200	[thread overview]
Message-ID: <613388f9-3e18-f99c-5f80-07d196138f60@gmail.com> (raw)
In-Reply-To: <20170823195225.GF4794@magnolia>

On 08/23/2017 09:52 PM, Darrick J. Wong wrote:
> The FMR_OF_LAST flag is applied to the last record in the returned
> dataset, which is not necessarily the last record in the filesystem.
> Correct the documentation to reflect the actual behavior of both
> getfsmap implementations.

Thanks, Darrick. Applied.

Cheers,

Michael


> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
>  man2/ioctl_getfsmap.2 |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man2/ioctl_getfsmap.2 b/man2/ioctl_getfsmap.2
> index 2a3cf06..047a624 100644
> --- a/man2/ioctl_getfsmap.2
> +++ b/man2/ioctl_getfsmap.2
> @@ -225,7 +225,7 @@ The
>  field contains a special value instead of an inode number.
>  .TP
>  .B FMR_OF_LAST
> -This is the last record in the filesystem.
> +This is the last record in the data set.
>  .RE
>  .PP
>  The
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2017-08-23 22:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 19:52 [PATCH] ioctl_getfsmap.2: correct semantics of FMR_OF_LAST flag Darrick J. Wong
2017-08-23 22:33 ` 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=613388f9-3e18-f99c-5f80-07d196138f60@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-xfs@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).