From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 4/5] mkfs: document sb_feat_args members
Date: Thu, 7 Dec 2017 20:27:22 -0800 [thread overview]
Message-ID: <20171208042722.GK19219@magnolia> (raw)
In-Reply-To: <3d8eeb94-8333-9d3d-7767-0a0267a2986e@sandeen.net>
On Thu, Dec 07, 2017 at 10:17:12PM -0600, Eric Sandeen wrote:
> Some of these are more self-explanatory than others ("nci?").
> Just mention the bit each one controls, and put them in order
> while we're at it. There are more comments about each bit
> near its definition.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
> mkfs/xfs_mkfs.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index f6e2fad..3f6315d 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -760,17 +760,17 @@ struct sb_feat_args {
> int log_version;
> int attr_version;
> int dir_version;
> - bool inode_align;
> - bool nci;
> - bool lazy_sb_counters;
> - bool projid32bit;
> - bool crcs_enabled;
> - bool dirftype;
> - bool finobt;
> - bool spinodes;
> - bool rmapbt;
> - bool reflink;
> - bool parent_pointers;
> + bool inode_align; /* XFS_SB_VERSION_ALIGNBIT */
> + bool nci; /* XFS_SB_VERSION_BORGBIT */
Is there a compelling reason for leaving all these weird names?
nci, borg, asciici...
"names case insensitive"
"buy organic ratty gallbladders"
"ascii case insensitive"
They're all kinda terrible, but at least I get the gist with the third one.
Otherwise looks ok,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
> + bool lazy_sb_counters; /* XFS_SB_VERSION2_LAZYSBCOUNTBIT */
> + bool parent_pointers; /* XFS_SB_VERSION2_PARENTBIT */
> + bool projid32bit; /* XFS_SB_VERSION2_PROJID32BIT */
> + bool crcs_enabled; /* XFS_SB_VERSION2_CRCBIT */
> + bool dirftype; /* XFS_SB_VERSION2_FTYPE */
> + bool finobt; /* XFS_SB_FEAT_RO_COMPAT_FINOBT */
> + bool spinodes; /* XFS_SB_FEAT_INCOMPAT_SPINODES */
> + bool rmapbt; /* XFS_SB_FEAT_RO_COMPAT_RMAPBT */
> + bool reflink; /* XFS_SB_FEAT_RO_COMPAT_REFLINK */
> bool nodalign;
> bool nortalign;
> };
> --
> 1.8.3.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-12-08 4:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 4:11 [PATCH 0/5] mkfs: minor tidyups Eric Sandeen
2017-12-08 4:13 ` [PATCH 1/5] mkfs: Don't emit default config message yet Eric Sandeen
2017-12-08 4:21 ` Darrick J. Wong
2017-12-08 4:54 ` Dave Chinner
2017-12-08 13:37 ` Eric Sandeen
2017-12-08 4:13 ` [PATCH 2/5] mkfs: remove unused m_uuid in sb_feat_args Eric Sandeen
2017-12-08 4:22 ` Darrick J. Wong
2017-12-08 4:15 ` [PATCH 3/5] mkfs: invert project id width boolean name Eric Sandeen
2017-12-08 4:18 ` Darrick J. Wong
2017-12-08 4:17 ` [PATCH 4/5] mkfs: document sb_feat_args members Eric Sandeen
2017-12-08 4:27 ` Darrick J. Wong [this message]
2017-12-08 4:59 ` Dave Chinner
2017-12-08 4:18 ` [PATCH 5/5] mkfs: remove use-once default macros Eric Sandeen
2017-12-08 4:27 ` Darrick J. Wong
2017-12-08 5:01 ` [PATCH 0/5] mkfs: minor tidyups Dave Chinner
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=20171208042722.GK19219@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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