From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Jesse Taube <jtaubepe@redhat.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
John Meneghini <jmeneghi@redhat.com>,
Daniel Wagner <dwagner@suse.de>
Subject: Re: [blktests v3 0/2] Test multipath and marginal ports
Date: Wed, 14 Oct 2026 21:00:35 +0900 [thread overview]
Message-ID: <as9uktniam6a8cLO@shinmob> (raw)
In-Reply-To: <20260828153029.853768-1-jtaubepe@redhat.com>
On Aug 28, 2026 / 11:30, Jesse Taube wrote:
> Tests for the upcoming nvme-fc: FPIN link integrity handling set.
> It tests for various multipath and marginal port
> scenarios, while confirming the port usage and state. The test is
> intended to emulate receiving an FPIN event in a multipath environment.
>
> In V3 various generic link checking code was move to common/nvme.
> This is so that it can be used by other tests to check if multipath
> working correctly, even on kernels that dont support marginal paths.
Thanks for the v3 patch. I applied it. Please note that I renumbered the test
case from 070 to 071.
prev parent reply other threads:[~2026-10-14 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 15:30 [blktests v3 0/2] Test multipath and marginal ports Jesse Taube
2026-08-28 15:30 ` [blktests v3 1/2] nvme: Add _setup_nvmet_port_marginal Jesse Taube
2026-08-28 15:30 ` [blktests v3 2/2] nvme/070: Test multipath and marginal ports Jesse Taube
2026-10-14 12:00 ` Shin'ichiro Kawasaki [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=as9uktniam6a8cLO@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=dwagner@suse.de \
--cc=jmeneghi@redhat.com \
--cc=jtaubepe@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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