From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Keith Busch <kbusch@kernel.org>
Cc: Keith Busch <kbusch@meta.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH blktests] nvme: test log page offsets
Date: Wed, 7 Feb 2024 05:19:53 +0000 [thread overview]
Message-ID: <cd04b339-e8a2-447b-b623-1c880e6c7612@nvidia.com> (raw)
In-Reply-To: <osl4dygp3c76pin62mumm42bs7t4hpooynfvsyqnda4acxxqeo@irad4vxvungc>
> Another idea is to separate the test case from the nvme group to a new group
> called "nvmedev" or "devcompat", which is dedicated to check that the storage
> devices work good with Linux storage stack. It will make it easier for the
> blktests users to understand the action to take, and which test group to run.
> What do you think?
>
>
apart from test being useful, above suggestions will streamline handling of
any testcase that falls into into device specific category, yet
maintaining the
flow of the exiting infrastructure ..
-ck
next prev parent reply other threads:[~2024-02-07 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 18:52 [PATCH blktests] nvme: test log page offsets Keith Busch
2024-02-05 22:30 ` Chaitanya Kulkarni
2024-02-06 6:02 ` Shinichiro Kawasaki
2024-02-06 6:41 ` Keith Busch
2024-02-06 16:50 ` Keith Busch
2024-02-07 4:32 ` Shinichiro Kawasaki
2024-02-07 5:19 ` Chaitanya Kulkarni [this message]
2024-02-07 5:52 ` Keith Busch
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=cd04b339-e8a2-447b-b623-1c880e6c7612@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-nvme@lists.infradead.org \
--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