From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2] nvme/core: Check for Security send/recv support before issuing commands.
Date: Fri, 17 Feb 2017 09:24:16 +0100 [thread overview]
Message-ID: <20170217082416.GA18090@lst.de> (raw)
In-Reply-To: <9daa1e48-90c9-9138-4683-4edafffbb613@intel.com>
On Thu, Feb 16, 2017@03:38:53PM -0700, Jon Derrick wrote:
> Looks fine,
> Reviewed-by: Jon Derrick <jonathan.derrick at intel.com>
I think we need to do this from nvme_reset before calling into
the OPAL code (or any other security protocol in the future).
I'll prepare a patch.
prev parent reply other threads:[~2017-02-17 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 22:17 [PATCH v2] nvme/core: Check for Security send/recv support before issuing commands Scott Bauer
2017-02-16 22:38 ` Jon Derrick
2017-02-17 8:24 ` Christoph Hellwig [this message]
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=20170217082416.GA18090@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 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.