From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Huang Jianan <huangjianan@oppo.com>
Cc: yh@oppo.com, kevin.liw@oppo.com, guoweichao@oppo.com,
linux-erofs@lists.ozlabs.org, guanyuwei@oppo.com
Subject: Re: [PATCH] AOSP: erofs-utils: increase val for WITH_ANDROID option
Date: Wed, 25 Aug 2021 15:25:52 +0800 [thread overview]
Message-ID: <YSXwgCND2Zf0sfl2@B-P7TQMD6M-0146.local> (raw)
In-Reply-To: <20210825033416.19868-1-huangjianan@oppo.com>
Hi Jianan,
On Wed, Aug 25, 2021 at 11:34:16AM +0800, Huang Jianan via Linux-erofs wrote:
Subject: AOSP: erofs-utils: increase val for AOSP-specific long options
> Signed-off-by: Huang Jianan <huangjianan@oppo.com>
> ---
> mkfs/main.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/mkfs/main.c b/mkfs/main.c
> index 10fe14d..9369b72 100644
> --- a/mkfs/main.c
> +++ b/mkfs/main.c
> @@ -45,10 +45,10 @@ static struct option long_options[] = {
> #endif
> {"max-extent-bytes", required_argument, NULL, 9},
> #ifdef WITH_ANDROID
> - {"mount-point", required_argument, NULL, 10},
> - {"product-out", required_argument, NULL, 11},
> - {"fs-config-file", required_argument, NULL, 12},
> - {"block-list-file", required_argument, NULL, 13},
> + {"mount-point", required_argument, NULL, 256},
> + {"product-out", required_argument, NULL, 257},
> + {"fs-config-file", required_argument, NULL, 258},
> + {"block-list-file", required_argument, NULL, 259},
> #endif
> {0, 0, 0, 0},
> };
> @@ -289,20 +289,20 @@ static int mkfs_parse_options_cfg(int argc, char *argv[])
> }
> break;
> #ifdef WITH_ANDROID
> - case 10:
> + case 256:
How about using larger numbers such as 512 for AOSP-specific options?
I'm afraid in the future we might bump up generic options to >= 256
like this as well.
Otherwise looks good to me.
Thanks,
Gao Xiang
next prev parent reply other threads:[~2021-08-25 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 3:34 [PATCH] AOSP: erofs-utils: increase val for WITH_ANDROID option Huang Jianan via Linux-erofs
2021-08-25 7:25 ` Gao Xiang [this message]
2021-08-25 7:34 ` Huang Jianan via Linux-erofs
2021-08-25 7:44 ` [PATCH v2] " Huang Jianan 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=YSXwgCND2Zf0sfl2@B-P7TQMD6M-0146.local \
--to=hsiangkao@linux.alibaba.com \
--cc=guanyuwei@oppo.com \
--cc=guoweichao@oppo.com \
--cc=huangjianan@oppo.com \
--cc=kevin.liw@oppo.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=yh@oppo.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).