From: hch@lst.de (Christoph Helwig)
Subject: NVMe target log page offset not supported
Date: Thu, 19 Oct 2017 10:51:11 +0200 [thread overview]
Message-ID: <20171019085111.GB14227@lst.de> (raw)
In-Reply-To: <A5F28D4A728A7E41839CDC5C3B5A01E887295CEF@FMSMSX103.amr.corp.intel.com>
On Wed, Oct 18, 2017@11:52:04PM +0000, Verkamp, Daniel wrote:
> Unfortunately, I don't have time right now to write and thoroughly test a patch for this, so I thought I'd at least make it known. It's on my todo list...
Yes, implementing it should be fairly easy, but I'd like to start
wanting test coverage for things like this.
Chaitanya has a really nice test framework, I think it might be a good
fit for that.
next prev parent reply other threads:[~2017-10-19 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 23:52 NVMe target log page offset not supported Verkamp, Daniel
2017-10-19 8:51 ` Christoph Helwig [this message]
2017-10-19 9:04 ` Johannes Thumshirn
2017-10-19 9:56 ` Chaitanya Kulkarni
2017-10-19 10:01 ` Sagi Grimberg
2017-10-19 10:38 ` Chaitanya Kulkarni
2017-10-19 10:18 ` Johannes Thumshirn
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=20171019085111.GB14227@lst.de \
--to=hch@lst.de \
/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