Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <b2004583-6e9c-9282-b59c-95cae9187378@huaweicloud.com>
Date:   Sun, 25 Jun 2023 16:13:16 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.10.0
Subject: Re: [PATCH v3 0/4] block/badblocks: fix badblocks setting error
To:     Ashok Raj <ashok_raj@linux.intel.com>, linan666@huaweicloud.com
Cc:     axboe@kernel.dk, dan.j.williams@intel.com,
        vishal.l.verma@intel.com, linux-block@vger.kernel.org,
        linux-kernel@vger.kernel.org, yukuai3@huawei.com,
        yi.zhang@huawei.com, houtao1@huawei.com, yangerkun@huawei.com,
        Ashok Raj <ashok.raj@intel.com>
References: <20230621172052.1499919-1-linan666@huaweicloud.com>
 <ZJL73Zhyq4d/oaXd@araj-dh-work>
From:   Li Nan <linan666@huaweicloud.com>
In-Reply-To: <ZJL73Zhyq4d/oaXd@araj-dh-work>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk


在 2023/6/21 21:32, Ashok Raj 写道:
> On Thu, Jun 22, 2023 at 01:20:48AM +0800, linan666@huaweicloud.com wrote:
>> From: Li Nan <linan122@huawei.com>
>>
>> This patch series fixes some simple bugs of setting badblocks and
>> optimizing struct badblocks. Coly Li has been trying to refactor badblocks
>> in patch series "badblocks improvement for multiple bad block ranges", but
>> the workload is significant. Before that, I will fix some easily triggered
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> You mean the refactor is going to take longer to complete?

Yes, refer to the link:
https://lore.kernel.org/all/20220721121152.4180-1-colyli@suse.de

> If so, maybe state it that way...
> 
> .

-- 
Thanks,
Nan