[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZJL73Zhyq4d/oaXd@araj-dh-work>
Date: Wed, 21 Jun 2023 06:32:13 -0700
From: Ashok Raj <ashok_raj@...ux.intel.com>
To: linan666@...weicloud.com
Cc: axboe@...nel.dk, linan122@...wei.com, dan.j.williams@...el.com,
vishal.l.verma@...el.com, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, yukuai3@...wei.com,
yi.zhang@...wei.com, houtao1@...wei.com, yangerkun@...wei.com,
Ashok Raj <ashok.raj@...el.com>
Subject: Re: [PATCH v3 0/4] block/badblocks: fix badblocks setting error
On Thu, Jun 22, 2023 at 01:20:48AM +0800, linan666@...weicloud.com wrote:
> From: Li Nan <linan122@...wei.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?
If so, maybe state it that way...
Powered by blists - more mailing lists