linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
	Minwoo Im <minwoo.im.dev@gmail.com>
Subject: [PATCH 0/3] blktests: nvme: Fix pass data of nvmet TCs
Date: Mon,  6 May 2019 00:06:08 +0900	[thread overview]
Message-ID: <20190505150611.15776-1-minwoo.im.dev@gmail.com> (raw)

Hi, Omar,

This patchset fixes mismatch between expected pass data and real data
printed out for nvmet testcases.

It has been long time to have changes for nvmet and nvme-cli.  The
following commits can explain why the pass data has to be updated.

About genctr:
  Commit b662a078 ("nvmet: enable Discovery Controller AENs")

About treq field:
- nvmet:
  Commit 9b95d2fb ("nvmet: expose support for fabrics SQ flow control
                    disable in treq")
- nvme-cli:
  Commit 2cf370c3 ("fabrics: support fabrics sq flow control disable")

Please correct me if I'm wrong here. :)

Thanks,

*** BLURB HERE ***

Minwoo Im (3):
  nvme: 002: fix nvmet pass data with loop
  nvme: 016: fix nvmet pass data with loop
  nvme: 017: fix nvmet pass data with loop

 tests/nvme/002.out | 2002 ++++++++++++++++++++++++++--------------------------
 tests/nvme/016.out |    4 +-
 tests/nvme/017.out |    4 +-
 3 files changed, 1005 insertions(+), 1005 deletions(-)

-- 
2.7.4


             reply	other threads:[~2019-05-05 15:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05 15:06 Minwoo Im [this message]
2019-05-05 15:06 ` [PATCH 2/3] nvme: 016: fix nvmet pass data with loop Minwoo Im
2019-05-06 16:26   ` Chaitanya Kulkarni
2019-05-05 15:06 ` [PATCH 3/3] nvme: 017: " Minwoo Im
2019-05-06 16:25   ` Chaitanya Kulkarni
     [not found] ` <20190505150611.15776-2-minwoo.im.dev@gmail.com>
     [not found]   ` <SN6PR04MB45274C423AA7C3CC3DBB5ED586300@SN6PR04MB4527.namprd04.prod.outlook.com>
2019-05-06 16:38     ` [PATCH 1/3] nvme: 002: " Minwoo Im
2019-05-06 16:46       ` Chaitanya Kulkarni
2019-05-06 16:54         ` Minwoo Im
2019-05-06 17:47           ` Chaitanya Kulkarni
2019-05-06 20:13             ` Minwoo Im
2019-05-06 23:01               ` Chaitanya Kulkarni
2019-05-06 23:23                 ` Minwoo Im
2019-05-07  1:38                   ` Chaitanya Kulkarni
2019-05-09  5:51                   ` Chaitanya Kulkarni
2019-05-09  6:15                     ` Minwoo Im
2019-05-07  6:20           ` Johannes Thumshirn
2019-05-07 10:23             ` Minwoo Im
2019-05-09  5:52               ` Chaitanya Kulkarni

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=20190505150611.15776-1-minwoo.im.dev@gmail.com \
    --to=minwoo.im.dev@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=osandov@osandov.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;
as well as URLs for NNTP newsgroup(s).