From: Christoph Hellwig <hch@lst.de>
To: Jon Derrick <jonathan.derrick@intel.com>
Cc: 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: Re: [PATCHv2 0/5] OPAL patche'd cont'd
Date: Sat, 18 Feb 2017 09:24:40 +0100 [thread overview]
Message-ID: <20170218082440.GA11798@lst.de> (raw)
In-Reply-To: <1487376029-22662-1-git-send-email-jonathan.derrick@intel.com>
On Fri, Feb 17, 2017 at 05:00:24PM -0700, Jon Derrick wrote:
> 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 next two since they haven't been pulled yet.
Next time please carry the reviewed-by tags over to make everyones
life easier.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCHv2 0/5] OPAL patche'd cont'd
Date: Sat, 18 Feb 2017 09:24:40 +0100 [thread overview]
Message-ID: <20170218082440.GA11798@lst.de> (raw)
In-Reply-To: <1487376029-22662-1-git-send-email-jonathan.derrick@intel.com>
On Fri, Feb 17, 2017@05:00:24PM -0700, Jon Derrick wrote:
> 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 next two since they haven't been pulled yet.
Next time please carry the reviewed-by tags over to make everyones
life easier.
next prev parent reply other threads:[~2017-02-18 8:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 0:00 [PATCHv2 0/5] OPAL patche'd cont'd Jon Derrick
2017-02-18 0:00 ` Jon Derrick
2017-02-18 0:00 ` [PATCHv2 1/5] block/sed: Use ssize_t on atom parsers to return errors Jon Derrick
2017-02-18 0:00 ` Jon Derrick
2017-02-18 0:00 ` [PATCHv2 2/5] block/sed: Add helper to qualify response tokens Jon Derrick
2017-02-18 0:00 ` Jon Derrick
2017-02-18 0:00 ` [PATCHv2 3/5] block/sed: Check received header lengths Jon Derrick
2017-02-18 0:00 ` Jon Derrick
2017-02-18 0:00 ` [PATCHv2 4/5] block/sed: Embed function data into the function sequence Jon Derrick
2017-02-18 0:00 ` Jon Derrick
2017-02-18 8:36 ` Christoph Hellwig
2017-02-18 8:36 ` Christoph Hellwig
2017-02-18 15:52 ` Scott Bauer
2017-02-18 15:52 ` Scott Bauer
2017-02-18 16:22 ` Christoph Hellwig
2017-02-18 16:22 ` Christoph Hellwig
2017-02-18 0:00 ` [PATCHv2 5/5] block/sed: Eliminate state variable Jon Derrick
2017-02-18 0:00 ` Jon Derrick
2017-02-18 8:36 ` Christoph Hellwig
2017-02-18 8:36 ` Christoph Hellwig
2017-02-18 8:24 ` Christoph Hellwig [this message]
2017-02-18 8:24 ` [PATCHv2 0/5] OPAL patche'd cont'd Christoph Hellwig
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=20170218082440.GA11798@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=jonathan.derrick@intel.com \
--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 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.