From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: mariusz.tkaczyk@intel.com, song@kernel.org,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
yukuai3@huawei.com, yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH md-6.12 0/7] md: enhance faulty chekcing for blocked handling
Date: Wed, 9 Oct 2024 10:52:16 +0200 [thread overview]
Message-ID: <05afc661-9aef-415f-a429-eade6e6a72a4@molgen.mpg.de> (raw)
In-Reply-To: <20240830072721.2112006-1-yukuai1@huaweicloud.com>
Dear Kuai,
Thank you for this patch series. Just a note about the typo in che*ck*ing.
Kind regards,
Paul
next prev parent reply other threads:[~2024-10-09 8:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 7:27 Yu Kuai
2024-08-30 7:27 ` [PATCH md-6.12 1/7] md: add a new helper rdev_blocked() Yu Kuai
2024-08-30 7:27 ` [PATCH md-6.12 2/7] md: don't wait faulty rdev in md_wait_for_blocked_rdev() Yu Kuai
2024-08-30 7:27 ` [PATCH md-6.12 3/7] md: don't record new badblocks for faulty rdev Yu Kuai
2024-08-30 10:28 ` Mariusz Tkaczyk
2024-08-31 1:14 ` Yu Kuai
2024-09-02 8:55 ` Mariusz Tkaczyk
2024-09-02 12:37 ` Yu Kuai
2024-08-30 7:27 ` [PATCH md-6.12 4/7] md/raid1: factor out helper to handle blocked rdev from raid1_write_request() Yu Kuai
2024-08-30 11:06 ` Mariusz Tkaczyk
2024-08-31 1:13 ` Yu Kuai
2024-08-30 7:27 ` [PATCH md-6.12 5/7] md/raid1: don't wait for Faulty rdev in wait_blocked_rdev() Yu Kuai
2024-08-30 7:27 ` [PATCH md-6.12 6/7] md/raid10: " Yu Kuai
2024-08-30 7:27 ` [PATCH md-6.12 7/7] md/raid5: don't set Faulty rdev for blocked_rdev Yu Kuai
2024-08-30 11:12 ` [PATCH md-6.12 0/7] md: enhance faulty chekcing for blocked handling Mariusz Tkaczyk
2024-10-09 7:14 ` Mariusz Tkaczyk
2024-10-10 12:38 ` Yu Kuai
2024-10-09 8:52 ` Paul Menzel [this message]
2024-10-10 12:40 ` Yu Kuai
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=05afc661-9aef-415f-a429-eade6e6a72a4@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@intel.com \
--cc=song@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®