Re: [PATCH blktests 0/3] tetss/nvme: fix nvme disc changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Chaitanya Kulkarni <chaitanyak@xxxxxxxxxx>, linux-block@xxxxxxxxxxxxxxx, linux-nvme@xxxxxxxxxxxxxxxxxxx
Subject: Re: [PATCH blktests 0/3] tetss/nvme: fix nvme disc changes
From: Sagi Grimberg <sagi@xxxxxxxxxxx>
Date: Wed, 12 Jan 2022 10:38:41 +0200
Cc: osandov@xxxxxx, Chaitanya Kulkarni <kch@xxxxxxxxxx>
In-reply-to: <20220112060614.73015-1-chaitanyak@nvidia.com>
References: <20220112060614.73015-1-chaitanyak@nvidia.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0

What is preventing this to break again?

Can we modify the tests to not rely on a consistent
output here. Perhaps just search/match the expected nvm subsystems
in the log page?

Follow-Ups:
- Re: [PATCH blktests 0/3] tetss/nvme: fix nvme disc changes
  - From: Chaitanya Kulkarni

References:
- [PATCH blktests 0/3] tetss/nvme: fix nvme disc changes
  - From: Chaitanya Kulkarni

Prev by Date: [PATCH blktests 3/3] tests/nvme/017: adjust to new nvme disc page output
Next by Date: [PATCH 4/4] bfq: Update cgroup information before merging bio
Previous by thread: [PATCH blktests 3/3] tests/nvme/017: adjust to new nvme disc page output
Next by thread: Re: [PATCH blktests 0/3] tetss/nvme: fix nvme disc changes
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux