From: Jirong Feng <jirong.feng@easystack.cn>
To: Sagi Grimberg <sagi@grimberg.me>, linux-nvme@lists.infradead.org
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH] nvmet: fix nvme status code when namespace is disabled
Date: Mon, 29 Apr 2024 19:34:07 +0800 [thread overview]
Message-ID: <8ef75533-3dc0-46c8-be27-504e5cd9a234@easystack.cn> (raw)
In-Reply-To: <20240428092540.77366-1-sagi@grimberg.me>
> Jirong Feng, can you please re-run the test as requested and verify
> that the I/O error goes away. If so, please reply with your "Tested-by"
> tag.
Having re-runned the test basing on kernel 6.9.0-rc5, the error does go
away.
Tested-by: Jirong Feng <jirong.feng@easystack.cn>
next prev parent reply other threads:[~2024-04-29 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 9:25 [PATCH] nvmet: fix nvme status code when namespace is disabled Sagi Grimberg
2024-04-29 5:14 ` Christoph Hellwig
2024-04-29 11:34 ` Jirong Feng [this message]
2024-04-29 11:52 ` Keith Busch
2024-04-30 3:38 ` Chaitanya Kulkarni
2024-05-23 9:49 ` Hannes Reinecke
2024-05-23 10:10 ` Sagi Grimberg
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=8ef75533-3dc0-46c8-be27-504e5cd9a234@easystack.cn \
--to=jirong.feng@easystack.cn \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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