From: Robert.Nocerino@holidaytaxi.info
To: nvdimm@lists.linux.dev <nvdimm@lists.linux.dev>
Subject: Re: [PATCH v6 5/7] badblocks: improve badblocks_check() for multiple ranges handling
Date: Tue, 21 Mar 2023 04:17:14 -0700 [thread overview]
Message-ID: <167939743487.8780.13802624212663338618@zittware.com> (raw)
In-Reply-To: <20220721121152.4180-6-colyli@suse.de>
[-- Attachment #1.1.1: Type: text/html, Size: 7079 bytes --]
[-- Attachment #1.2: Type: text/plain, Size: 133 bytes --]
Hello There,
If you've got inquiries regarding the business presentation, please get in touch with me.
VIEW DETAILS
Cheers,
next prev parent reply other threads:[~2023-03-21 14:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 12:11 [PATCH v6 0/7] badblocks improvement for multiple bad block ranges Coly Li
2022-07-21 12:11 ` [PATCH v6 1/7] badblocks: add more helper structure and routines in badblocks.h Coly Li
2022-09-21 12:16 ` Xiao Ni
2022-07-21 12:11 ` [PATCH v6 2/7] badblocks: add helper routines for badblock ranges handling Coly Li
2022-09-21 12:13 ` Xiao Ni
2023-08-11 16:57 ` Coly Li
2022-07-21 12:11 ` [PATCH v6 3/7] badblocks: improve badblocks_set() for multiple " Coly Li
2022-09-21 12:13 ` Xiao Ni
2023-08-11 16:57 ` Coly Li
2022-07-21 12:11 ` [PATCH v6 4/7] badblocks: improve badblocks_clear() " Coly Li
2022-09-21 15:26 ` Xiao Ni
2023-08-11 16:57 ` Coly Li
2023-08-11 16:58 ` Coly Li
2022-07-21 12:11 ` [PATCH v6 5/7] badblocks: improve badblocks_check() " Coly Li
2022-09-21 16:33 ` Xiao Ni
2022-09-23 15:17 ` 3507712
2022-10-28 17:50 ` Lynn.Figore
2022-12-20 13:25 ` Joy.Palmer
2023-03-21 11:17 ` Robert.Nocerino [this message]
2022-07-21 12:11 ` [PATCH v6 6/7] badblocks: switch to the improved badblock handling code Coly Li
2022-07-21 12:11 ` [PATCH v6 7/7] test: user space code to test badblocks APIs Coly Li
2023-05-23 2:38 ` [PATCH v6 0/7] badblocks improvement for multiple bad block ranges Li Nan
2023-05-23 4:38 ` Coly Li
2023-05-09 11:00 [PATCH v6 5/7] badblocks: improve badblocks_check() for multiple ranges handling tomas
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=167939743487.8780.13802624212663338618@zittware.com \
--to=robert.nocerino@holidaytaxi.info \
--cc=nvdimm@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.