From: Jon Derrick <jonathan.derrick@intel.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Jon Derrick <jonathan.derrick@intel.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Scott Bauer <scott.bauer@intel.com>,
Rafael Antognolli <rafael.antognolli@intel.com>,
Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>
Subject: [PATCH 0/5] OPAL patches cont'd
Date: Fri, 17 Feb 2017 15:56:13 -0700 [thread overview]
Message-ID: <1487372178-15715-1-git-send-email-jonathan.derrick@intel.com> (raw)
The first three in the series have been reviewed already but I wanted to
squash them with the next two since they haven't been pulled yet.
The latter 2 are an attempt to refactor some of the awkward func data
and state separation into a common struct
Jon Derrick (5):
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: embedded function data into the function sequence
block/sed: Eliminate state variable
block/sed-opal.c | 494 +++++++++++++++++++++++--------------------------------
1 file changed, 202 insertions(+), 292 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-02-17 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 22:56 Jon Derrick [this message]
2017-02-17 22:56 ` [PATCH 1/5] block/sed: Use ssize_t on atom parsers to return errors Jon Derrick
2017-02-17 22:56 ` [PATCH 2/5] block/sed: Add helper to qualify response tokens Jon Derrick
2017-02-17 22:56 ` [PATCH 3/5] block/sed: Check received header lengths Jon Derrick
2017-02-17 22:56 ` [PATCH 4/5] block/sed: embedded function data into the function sequence Jon Derrick
2017-02-17 22:56 ` [PATCH 5/5] block/sed: Eliminate state variable 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=1487372178-15715-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;
as well as URLs for NNTP newsgroup(s).