All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Song Liu <song@kernel.org>
Cc: Yu Kuai <yukuai1@huaweicloud.com>,
	mariusz.tkaczyk@intel.com, linux-raid@vger.kernel.org,
	linux-kernel@vger.kernel.org, yukuai3@huawei.com,
	yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH v2 0/7] md: enhance faulty checking for blocked handling
Date: Fri, 18 Oct 2024 14:56:43 +0200	[thread overview]
Message-ID: <20241018145643.0000788f@linux.intel.com> (raw)
In-Reply-To: <CAPhsuW4UCFbtrxXVfCaXFvCWYhb8He0tGSHq8UZ_4dWX=ZMs3A@mail.gmail.com>

On Thu, 17 Oct 2024 23:46:58 -0700
Song Liu <song@kernel.org> wrote:

> Mariusz, you have run some tests on v1, but didn't give your
> Tested-by tag. Would you mind rerun the test and reply with
> the tag?
> 
> Thanks,
> Song

Hi Song,
I see no functional difference between v1 and v2 feel free to add it.
I will be hard to rerun these tests right now.

Tested-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>

Thanks,
Mariusz

  reply	other threads:[~2024-10-18 12:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  1:16 [PATCH v2 0/7] md: enhance faulty checking for blocked handling Yu Kuai
2024-10-11  1:16 ` [PATCH v2 1/7] md: add a new helper rdev_blocked() Yu Kuai
2024-10-11  1:16 ` [PATCH v2 2/7] md: don't wait faulty rdev in md_wait_for_blocked_rdev() Yu Kuai
2024-10-30  1:22   ` Yu Kuai
2024-10-30  6:28     ` Song Liu
2024-10-11  1:16 ` [PATCH v2 3/7] md: don't record new badblocks for faulty rdev Yu Kuai
2024-10-11  1:16 ` [PATCH v2 4/7] md/raid1: factor out helper to handle blocked rdev from raid1_write_request() Yu Kuai
2024-10-11  1:16 ` [PATCH v2 5/7] md/raid1: don't wait for Faulty rdev in wait_blocked_rdev() Yu Kuai
2024-10-11  1:16 ` [PATCH v2 6/7] md/raid10: " Yu Kuai
2024-10-11  1:16 ` [PATCH v2 7/7] md/raid5: don't set Faulty rdev for blocked_rdev Yu Kuai
2024-10-18  6:46 ` [PATCH v2 0/7] md: enhance faulty checking for blocked handling Song Liu
2024-10-18 12:56   ` Mariusz Tkaczyk [this message]
2024-10-18 15:43     ` Song Liu

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=20241018145643.0000788f@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --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 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.