From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Gaoming (ming, consumer BG)" <gaoming20@huawei.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Liqingchao (sorp)" <sorp.liqingchao@huawei.com>,
"Shenchen (harry)" <harry.shen@huawei.com>,
"miaoxie (A)" <miaoxie@huawei.com>,
"yangfei (D)" <yangfei39@huawei.com>,
"Renlipeng (OS driver)" <renlipeng@huawei.com>
Subject: Re: 答复: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not integer,incompatible for ancient android devices
Date: Mon, 2 Jul 2018 08:16:54 -0400 [thread overview]
Message-ID: <20180702121654.GA15131@thunk.org> (raw)
In-Reply-To: <FDC91B229D965C458E3615E98C48ADDD0EC41D5F@dggemm511-mbx.china.huawei.com>
On Mon, Jul 02, 2018 at 09:34:28AM +0000, Gaoming (ming, consumer BG) wrote:
> I got it. You hate make_ext4fs, and me too.
> You don't like to merge this patch in upstream e2fsprogs to resolve the bug of make_ext4fs.
>
> Of course we will fix the bug on our ancient devices, we have to .
> If this problem fixed or this patch merges in latest e2fsprogs, we will backport the latest e2fsprogs.
> If not, we have no motivation to backport it.
>
> I don't know whether other android devices suffer this problem.
Can you be explicit and tell me how many Huawei devices uses a block
size of 1024? And can you help me understand *why* such a choice was made?
- Ted
next prev parent reply other threads:[~2018-07-02 12:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 11:54 [PATCH] ext4: e2fsprogs: fix inode bitmap num not integer,incompatible for ancient android devices GaoMing
2018-06-27 14:09 ` Theodore Y. Ts'o
2018-06-28 1:40 ` 答复: " Gaoming (ming, consumer BG)
2018-06-28 2:29 ` Theodore Y. Ts'o
2018-06-28 7:56 ` 答复: " Gaoming (ming, consumer BG)
2018-06-28 15:30 ` Theodore Y. Ts'o
2018-06-29 2:06 ` 答复: " Gaoming (ming, consumer BG)
2018-06-29 14:26 ` Theodore Y. Ts'o
2018-06-30 1:26 ` 答复: " Gaoming (ming, consumer BG)
2018-06-30 13:04 ` Theodore Y. Ts'o
2018-07-02 9:34 ` 答复: " Gaoming (ming, consumer BG)
2018-07-02 12:16 ` Theodore Y. Ts'o [this message]
2018-07-03 0:58 ` 答复: " Gaoming (ming, consumer BG)
2018-07-03 10:35 ` Theodore Y. Ts'o
2018-07-03 11:15 ` 答复: " Gaoming (ming, consumer BG)
2018-07-03 16:03 ` Theodore Y. Ts'o
2018-07-04 1:54 ` 答复: " Gaoming (ming, consumer BG)
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=20180702121654.GA15131@thunk.org \
--to=tytso@mit.edu \
--cc=gaoming20@huawei.com \
--cc=harry.shen@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=renlipeng@huawei.com \
--cc=sorp.liqingchao@huawei.com \
--cc=yangfei39@huawei.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).