From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: add support for Verify command opcode
Date: Sat, 11 May 2019 09:18:22 +0200 [thread overview]
Message-ID: <20190511071822.GA14764@lst.de> (raw)
In-Reply-To: <20190511000406.5458-1-kenneth.heitke@intel.com>
On Fri, May 10, 2019@06:04:06PM -0600, Kenneth Heitke wrote:
> This allows the Verify command to be sent using the
> NVME_IOCTL_SUBMIT_IO ioctl.
>
> Signed-off-by: Kenneth Heitke <kenneth.heitke at intel.com>
I think we've decided that NVME_IOCTL_SUBMIT_IO is deprecated and
everyone should be using NVME_IOCTL_IO_CMD instead.
Maybe we need to add an official deprecating warnings (probably
just a printk_once, maybe per process name?)
next prev parent reply other threads:[~2019-05-11 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 0:04 [PATCH] nvme: add support for Verify command opcode Kenneth Heitke
2019-05-11 7:18 ` Christoph Hellwig [this message]
2019-05-11 18:48 ` Heitke, Kenneth
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=20190511071822.GA14764@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