From: Keith Busch <kbusch@kernel.org>
To: Daniel Wagner <wagi@kernel.org>
Cc: James Smart <james.smart@broadcom.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Yi Zhang <yi.zhang@redhat.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Hannes Reinecke <hare@suse.de>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] nvmet-fc: fixes for blktests tests
Date: Mon, 15 Sep 2025 09:54:29 -0600 [thread overview]
Message-ID: <aMg2tdHWa0-dE5F8@kbusch-mbp> (raw)
In-Reply-To: <20250902-fix-nvmet-fc-v3-0-1ae1ecb798d8@kernel.org>
On Tue, Sep 02, 2025 at 12:21:59PM +0200, Daniel Wagner wrote:
> I've added the other two patches I've recenetly send out to this series
> for getting blktests with FC more stable. So this series containts all
> the latest versions of the patches flying around.
>
> What is missing are the changes for nvme/041. These patches need some
> more work and more review.
Thanks, applied to nvme-6.18.
prev parent reply other threads:[~2025-09-15 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 10:21 [PATCH v3 0/4] nvmet-fc: fixes for blktests tests Daniel Wagner
2025-09-02 10:22 ` [PATCH v3 1/4] nvmet-fc: move lsop put work to nvmet_fc_ls_req_op Daniel Wagner
2025-09-02 10:22 ` [PATCH v3 2/4] nvmet-fc: avoid scheduling association deletion twice Daniel Wagner
2025-09-02 10:22 ` [PATCH v3 3/4] nvmet-fcloop: call done callback even when remote port is gone Daniel Wagner
2025-09-02 10:22 ` [PATCH v3 4/4] nvme-fc: use lock accessing port_state and rport state Daniel Wagner
2025-09-02 10:27 ` Hannes Reinecke
2025-09-09 12:29 ` [PATCH v3 0/4] nvmet-fc: fixes for blktests tests Daniel Wagner
2025-09-15 15:54 ` Keith Busch [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=aMg2tdHWa0-dE5F8@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.com \
--cc=wagi@kernel.org \
--cc=yi.zhang@redhat.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.