From: osandov@osandov.com (Omar Sandoval)
Subject: [PATCH] test/nvme/003: add test case for patch "nvme: don't send keep-alives to the discovery controller"
Date: Fri, 6 Apr 2018 21:01:44 -0700 [thread overview]
Message-ID: <20180407040144.GB533@vader> (raw)
In-Reply-To: <20180327093147.10684-1-jthumshirn@suse.de>
On Tue, Mar 27, 2018@11:31:47AM +0200, Johannes Thumshirn wrote:
> Add a regression test for the patch titled "nvme: don't send
> keep-alives to the discovery controller".
>
> This patch creates a local loopback nvme target and then connects to
> it. If the patch is not applied we see two error messages in dmesg:
> "failed nvme_keep_alive_end_io error=" from the nvme host and "nvmet:
> unsupported cmd 24" from the nvme target. If the patch is applied
> dmesg is quiet.
>
> Signed-off-by: Johannes Thumshirn <jthumshirn at suse.de>
Applied, thanks, Johannes!
WARNING: multiple messages have this Message-ID (diff)
From: Omar Sandoval <osandov@osandov.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] test/nvme/003: add test case for patch "nvme: don't send keep-alives to the discovery controller"
Date: Fri, 6 Apr 2018 21:01:44 -0700 [thread overview]
Message-ID: <20180407040144.GB533@vader> (raw)
In-Reply-To: <20180327093147.10684-1-jthumshirn@suse.de>
On Tue, Mar 27, 2018 at 11:31:47AM +0200, Johannes Thumshirn wrote:
> Add a regression test for the patch titled "nvme: don't send
> keep-alives to the discovery controller".
>
> This patch creates a local loopback nvme target and then connects to
> it. If the patch is not applied we see two error messages in dmesg:
> "failed nvme_keep_alive_end_io error=" from the nvme host and "nvmet:
> unsupported cmd 24" from the nvme target. If the patch is applied
> dmesg is quiet.
>
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
Applied, thanks, Johannes!
next prev parent reply other threads:[~2018-04-07 4:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 9:28 [PATCH] nvme: don't send keep-alives to the discovery controller Johannes Thumshirn
2018-03-27 9:28 ` Johannes Thumshirn
2018-03-27 9:31 ` [PATCH] test/nvme/003: add test case for patch "nvme: don't send keep-alives to the discovery controller" Johannes Thumshirn
2018-03-27 9:31 ` Johannes Thumshirn
2018-04-07 4:01 ` Omar Sandoval [this message]
2018-04-07 4:01 ` Omar Sandoval
2018-03-28 8:04 ` [PATCH] nvme: don't send keep-alives to the discovery controller Christoph Hellwig
2018-03-28 8:04 ` Christoph Hellwig
2018-03-28 15:07 ` Keith Busch
2018-03-28 15:07 ` 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=20180407040144.GB533@vader \
--to=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 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.