From: Gao Xiang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: Li GuiFu <bluce.lee@aliyun.com>
Cc: linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH v2] AOSP: erofs-utils: add fs_config support
Date: Mon, 12 Oct 2020 07:48:36 +0800 [thread overview]
Message-ID: <20201011234221.GA26867@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <a4b4d4a8-46bc-87d2-eb8a-d1d010f9d76d@aliyun.com>
On Sun, Oct 11, 2020 at 04:53:24PM +0800, Li GuiFu wrote:
>
>
> 锟斤拷 2020/10/10 0:33, Li GuiFu 写锟斤拷:
> >
> >
> > 锟斤拷 2020/9/29 13:13, Gao Xiang 写锟斤拷:
> >> 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;
> >>
> >> include/erofs/config.h | 12 ++++++++++
> >> include/erofs/internal.h | 3 +++
> >> lib/inode.c | 49 +++++++++++++++++++++++++++++++++++++
> >> lib/xattr.c | 52 ++++++++++++++++++++++++++++++++++++++++
> >> mkfs/main.c | 29 +++++++++++++++++++++-
> >> 5 files changed, 144 insertions(+), 1 deletion(-)
> >>
> Please update the usage about mount-point
Ok, make sense. since it has been merged, will add another
patch to handle that.
Thanks,
Gao Xiang
>
prev parent reply other threads:[~2020-10-11 23:49 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
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 [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=20201011234221.GA26867@hsiangkao-HP-ZHAN-66-Pro-G1 \
--to=linux-erofs@lists.ozlabs.org \
--cc=bluce.lee@aliyun.com \
--cc=hsiangkao@aol.com \
/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).