From: Yue Hu <zbestahu@gmail.com>
To: Gao Xiang <xiang@kernel.org>
Cc: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH 2/2] erofs-utils: manpage: document `noinline_data' extended option
Date: Thu, 18 Nov 2021 11:59:26 +0800 [thread overview]
Message-ID: <20211118115926.000004a6.zbestahu@gmail.com> (raw)
In-Reply-To: <20211117015757.3323-2-xiang@kernel.org>
On Wed, 17 Nov 2021 09:57:57 +0800
Gao Xiang <xiang@kernel.org> wrote:
> From: Gao Xiang <hsiangkao@linux.alibaba.com>
>
> Add documentation for `noinline_data' as well.
>
> Fixes: 60549d52c3b6 ("erofs-utils: add "noinline_data" extended option")
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> ---
> man/mkfs.erofs.1 | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/man/mkfs.erofs.1 b/man/mkfs.erofs.1
> index f2e7d690c215..9c7788efbfec 100644
> --- a/man/mkfs.erofs.1
> +++ b/man/mkfs.erofs.1
> @@ -52,6 +52,9 @@ Forcely generate compact inodes (32-byte inodes) to output.
> .BI force-inode-extended
> Forcely generate extended inodes (64-byte inodes) to output.
> .TP
> +.BI noinline_data
> +Don't inline regular files for FSDAX support (Linux v5.15+).
> +.TP
Reviewed-by: Yue Hu <huyue2@yulong.com>
Thanks.
> .BI force-inode-blockmap
> Forcely generate inode chunk format in 4-byte block address array.
> .TP
prev parent reply other threads:[~2021-11-18 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 1:57 [PATCH 1/2] erofs-utils: mkfs: enable block map chunk format Gao Xiang
2021-11-17 1:57 ` [PATCH 2/2] erofs-utils: manpage: document `noinline_data' extended option Gao Xiang
2021-11-18 3:59 ` Yue Hu [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=20211118115926.000004a6.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=xiang@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