[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180702121654.GA15131@thunk.org>
Date: Mon, 2 Jul 2018 08:16:54 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: "Gaoming (ming, consumer BG)" <gaoming20@...wei.com>
Cc: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Liqingchao (sorp)" <sorp.liqingchao@...wei.com>,
"Shenchen (harry)" <harry.shen@...wei.com>,
"miaoxie (A)" <miaoxie@...wei.com>,
"yangfei (D)" <yangfei39@...wei.com>,
"Renlipeng (OS driver)" <renlipeng@...wei.com>
Subject: Re: 答复: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not integer,incompatible for
ancient android devices
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
Powered by blists - more mailing lists