From: Jon Derrick <jonathan.derrick@intel.com>
Cc: Jens Axboe <axboe@fb.com>,
Rafael Antognolli <rafael.antognolli@intel.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
Jon Derrick <jonathan.derrick@intel.com>,
Christoph Hellwig <hch@lst.de>,
Scott Bauer <scott.bauer@intel.com>
Subject: [PATCHv3 0/4] OPAL patches cont'd
Date: Tue, 21 Feb 2017 11:44:32 -0700 [thread overview]
Message-ID: <1487702676-10658-1-git-send-email-jonathan.derrick@intel.com> (raw)
v2->v3:
Squashed 5/5 into 4/5
Changed opal_step structs back to const
Cleaned up opal_lock_unlock
v1->v2:
Moved misplaced code from 5/5 to 4/5
The first three in the series have been reviewed already but I wanted to
squash them with the last patch since they haven't been pulled yet.
The last patch is an attempt to refactor some of the awkward func data
and state separation into a common struct
Jon Derrick (4):
block/sed: Use ssize_t on atom parsers to return errors
block/sed: Add helper to qualify response tokens
block/sed: Check received header lengths
block/sed: Embed function data into the function sequence
block/sed-opal.c | 551 +++++++++++++++++++++++--------------------------------
1 file changed, 225 insertions(+), 326 deletions(-)
--
1.8.3.1
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2017-02-21 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 18:44 Jon Derrick [this message]
2017-02-21 18:44 ` [PATCHv3 1/4] block/sed: Use ssize_t on atom parsers to return errors Jon Derrick
2017-02-21 18:44 ` [PATCHv3 2/4] block/sed: Add helper to qualify response tokens Jon Derrick
2017-02-21 18:44 ` [PATCHv3 3/4] block/sed: Check received header lengths Jon Derrick
2017-02-21 18:44 ` [PATCHv3 4/4] block/sed: Embed function data into the function sequence Jon Derrick
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=1487702676-10658-1-git-send-email-jonathan.derrick@intel.com \
--to=jonathan.derrick@intel.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=rafael.antognolli@intel.com \
--cc=scott.bauer@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox