From: Li Nan <linan666@huaweicloud.com>
To: Ira Weiny <ira.weiny@intel.com>, Coly Li <colyli@suse.de>,
linux-raid@vger.kernel.org, nvdimm@lists.linux.dev,
linux-block@vger.kernel.org
Cc: Dan Williams <dan.j.williams@intel.com>,
Geliang Tang <geliang.tang@suse.com>,
Hannes Reinecke <hare@suse.de>, Jens Axboe <axboe@kernel.dk>,
NeilBrown <neilb@suse.de>, Richard Fan <richard.fan@suse.com>,
Vishal L Verma <vishal.l.verma@intel.com>,
Wols Lists <antlists@youngman.org.uk>, Xiao Ni <xni@redhat.com>
Subject: Re: [PATCH v7 0/6] badblocks improvement for multiple bad block ranges
Date: Sat, 23 Dec 2023 14:46:33 +0800 [thread overview]
Message-ID: <914de4d4-0191-d812-778e-fc56b5898dc9@huaweicloud.com> (raw)
In-Reply-To: <6585dd1299942_ab808294c4@iweiny-mobl.notmuch>
Hi, Ira
在 2023/12/23 3:01, Ira Weiny 写道:
>
> Just in case I missed anyone on this original thread I've found issues
> with this series which I emailed Coly about here:
>
> https://lore.kernel.org/all/6585d5fda5183_9f731294b9@iweiny-mobl.notmuch/
>
> Ira
>
I have also noticed this issue recently and try to fix it in:
https://lore.kernel.org/linux-block/20231223063728.3229446-4-linan666@huaweicloud.com/T/#u
--
Thanks,
Nan
prev parent reply other threads:[~2023-12-23 6:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 17:05 [PATCH v7 0/6] badblocks improvement for multiple bad block ranges Coly Li
2023-08-11 17:05 ` [PATCH v7 1/6] badblocks: add more helper structure and routines in badblocks.h Coly Li
2023-08-11 17:05 ` [PATCH v7 2/6] badblocks: add helper routines for badblock ranges handling Coly Li
2023-09-02 14:21 ` Xiao Ni
2023-08-11 17:05 ` [PATCH v7 3/6] badblocks: improve badblocks_set() for multiple " Coly Li
2023-09-03 1:20 ` Xiao Ni
2023-08-11 17:05 ` [PATCH v7 4/6] badblocks: improve badblocks_clear() " Coly Li
2023-09-03 1:56 ` Xiao Ni
2023-08-11 17:05 ` [PATCH v7 5/6] badblocks: improve badblocks_check() " Coly Li
2023-09-03 3:26 ` Xiao Ni
2023-08-11 17:05 ` [PATCH v7 6/6] badblocks: switch to the improved badblock handling code Coly Li
2023-09-03 3:27 ` Xiao Ni
2023-08-11 17:05 ` [PATCH] test: user space code to test badblocks APIs Coly Li
2023-09-26 1:47 ` [PATCH v7 0/6] badblocks improvement for multiple bad block ranges Geliang Tang
2023-09-26 6:44 ` Jens Axboe
2023-12-22 19:01 ` Ira Weiny
2023-12-23 6:46 ` Li Nan [this message]
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=914de4d4-0191-d812-778e-fc56b5898dc9@huaweicloud.com \
--to=linan666@huaweicloud.com \
--cc=antlists@youngman.org.uk \
--cc=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=dan.j.williams@intel.com \
--cc=geliang.tang@suse.com \
--cc=hare@suse.de \
--cc=ira.weiny@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nvdimm@lists.linux.dev \
--cc=richard.fan@suse.com \
--cc=vishal.l.verma@intel.com \
--cc=xni@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).