From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: sandeen@sandeen.net, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/4] man: update mkfs.xfs inode flag option documentation
Date: Mon, 17 Aug 2020 07:54:09 +0100 [thread overview]
Message-ID: <20200817065409.GE23516@infradead.org> (raw)
In-Reply-To: <159736125533.3063459.18063990185908155478.stgit@magnolia>
On Thu, Aug 13, 2020 at 04:27:35PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> The mkfs manpage says that the extent size, cow extent size, realtime,
> and project id inheritance bits are passed on to "newly created
> children". This isn't technically true -- it's only passed on to newly
> created regular files and directories. It is not passed on to special
> files.
>
> Fix this minor inaccuracy in the documentation.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2020-08-17 6:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 23:27 [PATCH v2 0/4] xfsprogs: various small enhancements Darrick J. Wong
2020-08-13 23:27 ` [PATCH 1/4] xfs_db: fix nlink usage in check Darrick J. Wong
2020-08-17 6:53 ` Christoph Hellwig
2020-08-17 11:25 ` Carlos Maiolino
2020-08-13 23:27 ` [PATCH 2/4] xfs_db: report the inode dax flag Darrick J. Wong
2020-08-17 6:53 ` Christoph Hellwig
2020-08-17 11:26 ` Carlos Maiolino
2020-08-13 23:27 ` [PATCH 3/4] man: update mkfs.xfs inode flag option documentation Darrick J. Wong
2020-08-17 6:54 ` Christoph Hellwig [this message]
2020-08-17 11:27 ` Carlos Maiolino
2020-08-13 23:27 ` [PATCH 4/4] mkfs: allow setting dax flag on root directory Darrick J. Wong
2020-08-17 6:54 ` Christoph Hellwig
2020-08-17 11:30 ` Carlos Maiolino
2020-08-17 15:41 ` Darrick J. Wong
2020-08-17 15:43 ` [PATCH v2 " Darrick J. Wong
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=20200817065409.GE23516@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--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