From: Li Guifu <blucerlee@gmail.com>
To: Gao Xiang <hsiangkao@aol.com>,
Li Guifu <bluce.liguifu@huawei.com>,
linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH 2/2] erofs-utils: complete extended inode support
Date: Sun, 6 Oct 2019 00:15:32 +0800 [thread overview]
Message-ID: <a9543a49-52e4-9a79-a402-14794e1a17d5@gmail.com> (raw)
In-Reply-To: <20191004204630.22696-2-hsiangkao@aol.com>
> From: Gao Xiang <gaoxiang25@huawei.com>
>
> There is no requirement to use extended inode (v2)
> for Android, but it's obviously useful for wider
> use cases.
>
> extended inode was partially supported by obsoleted_mkfs,
> complete for new erofs-utils as well.
>
> Signed-off-by: Gao Xiang <gaoxiang25@huawei.com>
It looks good
Reviewed-by: Li Guifu <blucerlee@gmail.com>
Tested-by: Li Guifu <blucerlee@gmail.com>
Thanks,
next prev parent reply other threads:[~2019-10-05 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 20:46 [PATCH 1/2] erofs-utils: support 64-bit internal buffer cache Gao Xiang via Linux-erofs
2019-10-04 20:46 ` [PATCH 2/2] erofs-utils: complete extended inode support Gao Xiang via Linux-erofs
2019-10-05 16:15 ` Li Guifu [this message]
2019-10-05 16:25 ` [PATCH 1/2] erofs-utils: support 64-bit internal buffer cache Li Guifu
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=a9543a49-52e4-9a79-a402-14794e1a17d5@gmail.com \
--to=blucerlee@gmail.com \
--cc=bluce.liguifu@huawei.com \
--cc=hsiangkao@aol.com \
--cc=linux-erofs@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).