From: Eric Sandeen <sandeen@sandeen.net>
To: Mark Tingueyl <tinguely@sgi.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: fix xfsctl manual XFS_IOC_FSSETXATTR valid fields
Date: Tue, 23 Sep 2014 11:04:01 -0500 [thread overview]
Message-ID: <542199F1.4040207@sandeen.net> (raw)
In-Reply-To: <20140923154140.315778789@sgi.com>
On 9/23/14 10:41 AM, Mark Tingueyl wrote:
> The xfsctl manual page fails to mention that fsx_projid is a
> setable field.
>
> Signed-off-by: Mark Tinguely <tinguely@sgi.com>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
p.s. You might want to fix your name in your email client, Mr. Tingueyl ;)
> ---
> man/man3/xfsctl.3 | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> Index: b/man/man3/xfsctl.3
> ===================================================================
> --- a/man/man3/xfsctl.3
> +++ b/man/man3/xfsctl.3
> @@ -245,9 +245,10 @@ Set additional attributes associated wit
> The final argument points to a variable of type
> .BR "struct fsxattr" ,
> but only the following fields are used in this call:
> -.B fsx_xflags
> +.BR fsx_xflags ,
> +.B fsx_extsize
> and
> -.BR fsx_extsize .
> +.BR fsx_projid .
> The
> .B fsx_xflags
> realtime file bit and the file's extent size may be changed only
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-09-23 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 15:41 [PATCH] xfsprogs: fix xfsctl manual XFS_IOC_FSSETXATTR valid fields Mark Tingueyl
2014-09-23 16:04 ` Eric Sandeen [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=542199F1.4040207@sandeen.net \
--to=sandeen@sandeen.net \
--cc=tinguely@sgi.com \
--cc=xfs@oss.sgi.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