From: Scott Bauer <scott.bauer@intel.com>
To: linux-block@vger.kernel.org
Cc: axboe@fb.com, keith.busch@intel.com,
linux-nvme@lists.infradead.org, hch@lst.de,
jonathan.derrick@intel.com
Subject: Final opal patches for rc1
Date: Wed, 22 Feb 2017 10:15:05 -0700 [thread overview]
Message-ID: <1487783708-16285-1-git-send-email-scott.bauer@intel.com> (raw)
These are the final changes for rc1.
Patch 1 contains some code to clean up an opal structure if something changes
at runtime. (already reviewed by Christoph)
Patch 2 contains changes to the nvme driver to use the above patch. If a new
FW is loaded and we no longer support opal we clean up. This patch is based off
code from Keith and Christoph.
Patch 3 is a one line change to propagate an original error messaage to user
land instead of the return status of the session termination code.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2017-02-22 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 17:15 Scott Bauer [this message]
2017-02-22 17:15 ` [PATCH 1/3] block/sed-opal: Introduce free_opal_dev to free the structure and clean up state Scott Bauer
2017-02-22 17:15 ` [PATCH 2/3] nvme/pci: re-check security protocol support after reset Scott Bauer
2017-02-22 17:15 ` [PATCH 3/3] block/sed-opal: Propagate original error message to userland Scott Bauer
2017-02-23 18:57 ` Final opal patches for rc1 Jens Axboe
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=1487783708-16285-1-git-send-email-scott.bauer@intel.com \
--to=scott.bauer@intel.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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).