From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Nilay Shroff <nilay@linux.ibm.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>,
"dwagner@suse.de" <dwagner@suse.de>, "hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"gjoyce@linux.ibm.com" <gjoyce@linux.ibm.com>
Subject: Re: [PATCHv3 0/2] add nvme test for creating sleep while atomic kernel BUG
Date: Mon, 9 Dec 2024 07:16:30 +0000 [thread overview]
Message-ID: <442a8cd8-bfb3-443b-93c5-e31f95f3f5c4@nvidia.com> (raw)
In-Reply-To: <20241206111812.489140-1-nilay@linux.ibm.com>
On 12/6/24 03:18, Nilay Shroff wrote:
> Hi,
>
> There're two patches in this series. The first patch is a preparation patch
> for reusing a common function nvmf_wait_for_ns from multiple nvme test scripts.
> The second patch adds a new nvme regression[1] test for commit 505363957fad
> ("nvmet: fix nvme status code when namespace is disabled").
>
> For fixing regression, as suggested by Christoph[2], I would send a separate
> patch upstream.
>
> [1]https://lore.kernel.org/linux-nvme/tqcy3sveity7p56v7ywp7ssyviwcb3w4623cnxj3knoobfcanq@yxgt2mjkbkam/
> [2]https://lore.kernel.org/linux-nvme/20241022070252.GA11389@lst.de/
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2024-12-09 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 11:18 [PATCHv3 0/2] add nvme test for creating sleep while atomic kernel BUG Nilay Shroff
2024-12-06 11:18 ` [PATCHv3 1/2] nvme/052: move nvmf_wait_for_ns() to common/nvme Nilay Shroff
2024-12-06 12:27 ` Daniel Wagner
2024-12-24 11:29 ` Sagi Grimberg
2024-12-06 11:18 ` [PATCHv3 2/2] nvme: add test for writing to file-ns just after disabling it Nilay Shroff
2024-12-06 12:32 ` Daniel Wagner
2024-12-06 12:50 ` Nilay Shroff
2024-12-24 11:29 ` Sagi Grimberg
2024-12-09 7:16 ` Chaitanya Kulkarni [this message]
2024-12-09 11:50 ` [PATCHv3 0/2] add nvme test for creating sleep while atomic kernel BUG Shinichiro Kawasaki
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=442a8cd8-bfb3-443b-93c5-e31f95f3f5c4@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=dwagner@suse.de \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox