From: Coly Li <colyli@suse.de>
To: Geliang Tang <geliang.tang@suse.com>
Cc: nvdimm@lists.linux.dev, linux-block@vger.kernel.org,
linux-raid@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
Jens Axboe <axboe@kernel.dk>, NeilBrown <neilb@suse.de>,
Vishal L Verma <vishal.l.verma@intel.com>
Subject: Re: [PATCH v3 2/6] badblocks: add helper routines for badblock ranges handling
Date: Fri, 10 Dec 2021 14:57:20 +0800 [thread overview]
Message-ID: <a608949d-86ea-b7fd-c0c6-6dd6614202c7@suse.de> (raw)
In-Reply-To: <20211209072251.GA26976@dhcp-10-157-36-190>
On 12/9/21 3:22 PM, Geliang Tang wrote:
> Hi Coly,
>
> Thanks for this new version!
Thank you so much for the review comments. I fix all the typos and
change the code as you suggested with dropping extra local variables.
The modification will be posted in next version.
Coly Li
[snip]
next prev parent reply other threads:[~2021-12-10 6:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 12:52 [PATCH v4 0/6] badblocks improvement for multiple bad block ranges Coly Li
2021-12-02 12:52 ` [PATCH v3 1/6] badblocks: add more helper structure and routines in badblocks.h Coly Li
2021-12-02 12:52 ` [PATCH v3 2/6] badblocks: add helper routines for badblock ranges handling Coly Li
2021-12-09 7:22 ` Geliang Tang
2021-12-10 6:57 ` Coly Li [this message]
2021-12-02 12:52 ` [PATCH v3 3/6] badblocks: improvement badblocks_set() for multiple " Coly Li
2021-12-09 7:28 ` Geliang Tang
2021-12-09 18:37 ` Wols Lists
2021-12-10 6:55 ` Coly Li
2021-12-02 12:52 ` [PATCH v3 4/6] badblocks: improve badblocks_clear() " Coly Li
2021-12-09 7:35 ` Geliang Tang
2021-12-02 12:52 ` [PATCH v3 5/6] badblocks: improve badblocks_check() " Coly Li
2021-12-02 12:52 ` [PATCH v3 6/6] badblocks: switch to the improved badblock handling code Coly Li
2021-12-02 12:52 ` [PATCH] test: user space code to test badblocks APIs Coly Li
-- strict thread matches above, loose matches on Subject: below --
2021-09-13 16:36 [PATCH v3 0/7] badblocks improvement for multiple bad block ranges Coly Li
2021-09-13 16:36 ` [PATCH v3 2/6] badblocks: add helper routines for badblock ranges handling Coly Li
2021-09-27 7:25 ` Geliang Tang
2021-09-27 8:17 ` Coly Li
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=a608949d-86ea-b7fd-c0c6-6dd6614202c7@suse.de \
--to=colyli@suse.de \
--cc=axboe@kernel.dk \
--cc=geliang.tang@suse.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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).