From: Chao Yu <yuchao0@huawei.com>
To: Gao Xiang <hsiangkao@aol.com>, Li Guifu <bluce.lee@aliyun.com>,
Li Guifu <bluce.liguifu@huawei.com>,
<linux-erofs@lists.ozlabs.org>
Subject: Re: [PATCH v2] AOSP: erofs-utils: add fs_config support
Date: Sat, 10 Oct 2020 15:31:47 +0800 [thread overview]
Message-ID: <8f2addff-8a46-2cb6-5d72-5a0ba2f96dda@huawei.com> (raw)
In-Reply-To: <20201009023048.GA16011@hsiangkao-HP-ZHAN-66-Pro-G1>
On 2020/10/9 10:32, Gao Xiang via Linux-erofs wrote:
> On Wed, Oct 07, 2020 at 11:02:18PM +0800, Gao Xiang via Linux-erofs wrote:
>> On Tue, Sep 29, 2020 at 01:13:02PM +0800, Gao Xiang wrote:
>>> So that mkfs can directly generate images with fs_config.
>>> All code for AOSP is wraped up with WITH_ANDROID macro.
>>>
>>> Signed-off-by: Gao Xiang <hsiangkao@aol.com>
>>> ---
>>> changes since v1:
>>> - fix compile issues on Android / Linux build;
>>> - tested with Android system booting;
>>
>> Guifu, some feedback on this?
>> I'd like to merge it for AOSP preparation.
>
> I will merge this if still no response at the end of this
> week. Since this main logic has already been used by other
> Android vendors for months and I do need to go forward on
> AOSP stuff.
Good job! :)
Acked-by: Chao Yu <yuchao0@huawei.com>
Thanks,
>
> Thanks,
> Gao Xiang
>
>>
> .
>
next prev parent reply other threads:[~2020-10-10 7:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200928213549.17580-1-hsiangkao.ref@aol.com>
2020-09-28 21:35 ` [RFC PATCH] AOSP: erofs-utils: add fs_config support Gao Xiang via Linux-erofs
2020-09-29 5:13 ` [PATCH v2] " Gao Xiang via Linux-erofs
2020-10-07 15:02 ` Gao Xiang via Linux-erofs
2020-10-09 2:32 ` Gao Xiang via Linux-erofs
2020-10-10 7:31 ` Chao Yu [this message]
2020-10-10 12:18 ` Gao Xiang via Linux-erofs
[not found] ` <7e4490c0-0a3d-0ceb-98ca-73d5eb69932d@aliyun.com>
2020-10-11 8:53 ` Li GuiFu via Linux-erofs
2020-10-11 23:48 ` Gao Xiang via Linux-erofs
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=8f2addff-8a46-2cb6-5d72-5a0ba2f96dda@huawei.com \
--to=yuchao0@huawei.com \
--cc=bluce.lee@aliyun.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).