All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: John Meneghini <jmeneghi@redhat.com>
Cc: Jesse Taube <jtaubepe@redhat.com>,
	linux-block@vger.kernel.org,  linux-nvme@lists.infradead.org,
	Daniel Wagner <dwagner@suse.de>
Subject: Re: [PATCH v2 0/2] Test multipath and marginal ports
Date: Sun, 23 Aug 2026 21:24:57 +0900	[thread overview]
Message-ID: <aorlybK-WA8TEVUP@shinhome> (raw)
In-Reply-To: <0d3cb83e-a4b6-414d-8756-fafd4a8238bc@redhat.com>

On Aug 19, 2026 / 17:49, John Meneghini wrote:
[...]
> So I can recommend that Shinichiro test these patches with the current upstream kernel patches:
> 
>   https://lore.kernel.org/linux-nvme/20260812181300.3712426-1-jtaubepe@redhat.com/
> But there will be another version of Kernel patches and a V3 of this patch set will be forth coming.

Jesse, thanks for this v2 series. The blktests side patches look good to me.
Also I ran the new test case with the kernel side patches on top of v7.2 kernel,
and the test case passed. Good. I think the last piece is the kernel side
patches. I will wait the series get settled.


      parent reply	other threads:[~2026-08-23 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 20:04 [PATCH v2 0/2] Test multipath and marginal ports Jesse Taube
2026-08-19 20:04 ` [PATCH v2 1/2] nvme: Add _setup_nvmet_port_marginal Jesse Taube
2026-08-19 20:04 ` [PATCH v2 2/2] nvme/070: Test multipath and marginal ports Jesse Taube
2026-08-19 21:49 ` [PATCH v2 0/2] " John Meneghini
2026-08-20 14:09   ` John Meneghini
2026-08-23 12:24   ` 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=aorlybK-WA8TEVUP@shinhome \
    --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 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.