All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: <linux-block@vger.kernel.org>, <linux-nvme@lists.infradead.org>
Cc: <osandov@fb.com>, Chaitanya Kulkarni <kch@nvidia.com>
Subject: [PATCH blktests 3/3] tests/nvme/017: adjust to new nvme disc page output
Date: Tue, 11 Jan 2022 22:06:14 -0800	[thread overview]
Message-ID: <20220112060614.73015-4-chaitanyak@nvidia.com> (raw)
In-Reply-To: <20220112060614.73015-1-chaitanyak@nvidia.com>

From: Chaitanya Kulkarni <kch@nvidia.com>

The latest code counts and prints the dicovery subsystem.
Update expected output file.

Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
---
 tests/nvme/017.out | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/tests/nvme/017.out b/tests/nvme/017.out
index 14a3164..12787f7 100644
--- a/tests/nvme/017.out
+++ b/tests/nvme/017.out
@@ -1,6 +1,9 @@
 Running nvme/017
-Discovery Log Number of Records 1, Generation counter X
+Discovery Log Number of Records 2, Generation counter X
 =====Discovery Log Entry 0======
 trtype:  loop
+subnqn:  nqn.2014-08.org.nvmexpress.discovery
+=====Discovery Log Entry 1======
+trtype:  loop
 subnqn:  blktests-subsystem-1
 Test complete
-- 
2.29.0


  parent reply	other threads:[~2022-01-12  6:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  6:06 [PATCH blktests 0/3] tetss/nvme: fix nvme disc changes Chaitanya Kulkarni
2022-01-12  6:06 ` [PATCH blktests 1/3] tests/nvme/002: adjust to new nvme disc page output Chaitanya Kulkarni
2022-01-12  6:06 ` [PATCH blktests 2/3] tests/nvme/016: " Chaitanya Kulkarni
2022-01-12  6:06 ` Chaitanya Kulkarni [this message]
2022-01-12  8:38 ` [PATCH blktests 0/3] tetss/nvme: fix nvme disc changes Sagi Grimberg
2022-01-12 17:55   ` Chaitanya Kulkarni
2022-01-12 22:06     ` 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=20220112060614.73015-4-chaitanyak@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=osandov@fb.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.