From: Alex Elder <aelder@sgi.com>
To: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH VER 8] xfsprogs: projid32bit handling
Date: Sat, 09 Oct 2010 16:33:18 -0500 [thread overview]
Message-ID: <1286659998.5392.4.camel@doink> (raw)
In-Reply-To: <1286179438-18282-1-git-send-email-arekm@maven.pl>
On Mon, 2010-10-04 at 10:03 +0200, Arkadiusz Miśkiewicz wrote:
> Add projid32bit handling to userspace. mkfs.xfs is able to enable this
> feature for new filesystems. xfs_db knows what projid_lo/hi are.
>
> Signed-off-by: Arkadiusz Miśkiewicz <arekm@maven.pl>
This looks good. I tested it with your update for xfstests
and my earlier concerns seem to have been addressed.
I've already committed this change, I just wanted to
make sure you knew it's (finally) in.
Reviewed-by: Alex Elder <aelder@sgi.com>
> ---
>
> version 7 news:
> - xfs_admin can now easily enable projid32bit support
>
> version 8 news:
> - xfs_logprint now prints single 32bit projid instead of two
> 16bit projid_{lo,hi}. Thus we get the same output format
> as before.
> - use %u for displaying projid (instead of %d)
> - projid32bit flag in mkfs.xfs output separated by coma
> - bs_projid is back as bs_projid_lo + define for compatibility
> - man page formatting fix
>
> db/check.c | 2 +-
> db/inode.c | 6 ++++--
> db/sb.c | 6 ++++++
> db/xfs_admin.sh | 5 +++--
> include/xfs_dinode.h | 5 +++--
> include/xfs_fs.h | 17 +++++++++++++++--
> include/xfs_inode.h | 25 ++++++++++++++++++++++---
> include/xfs_sb.h | 17 ++++++++++++++++-
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-09 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 8:03 [PATCH VER 8] xfsprogs: projid32bit handling Arkadiusz Miśkiewicz
2010-10-09 21:33 ` Alex Elder [this message]
2010-10-09 21:47 ` Arkadiusz Miskiewicz
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=1286659998.5392.4.camel@doink \
--to=aelder@sgi.com \
--cc=arekm@maven.pl \
--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