From: Jens Axboe <axboe@fb.com>
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>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCHv4 0/4] OPAL patches, cont'd
Date: Tue, 21 Feb 2017 19:42:55 -0700 [thread overview]
Message-ID: <a75babc1-5a9d-2979-514a-5fea19370084@fb.com> (raw)
In-Reply-To: <1487703556-19913-1-git-send-email-jonathan.derrick@intel.com>
On 02/21/2017 11:59 AM, Jon Derrick wrote:
> v3->v4:
> Passes in 'lock_held' into opal_lock_unlock() so we don't need to
> mutex_trylock(). I wasn't totally confident in that approach anyways.
>
> 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
Guys, where are we at with this? I'm shipping off some more fixes
for -rc1 soon, and I'd really like to get this wrapped up sooner
rather than later.
--
Jens Axboe
next prev parent reply other threads:[~2017-02-22 2:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 18:59 [PATCHv4 0/4] OPAL patches, cont'd Jon Derrick
2017-02-21 18:59 ` [PATCHv4 4/4] block/sed: Embed function data into the function sequence Jon Derrick
2017-02-21 23:03 ` Scott Bauer
2017-02-22 7:13 ` Christoph Hellwig
2017-02-22 14:35 ` Jon Derrick
2017-02-22 16:10 ` Jens Axboe
2017-02-22 16:13 ` Scott Bauer
2017-02-22 16:47 ` Jens Axboe
2017-02-22 17:22 ` Keith Busch
2017-02-22 2:42 ` Jens Axboe [this message]
2017-02-22 3:14 ` [PATCHv4 0/4] OPAL patches, cont'd Scott Bauer
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=a75babc1-5a9d-2979-514a-5fea19370084@fb.com \
--to=axboe@fb.com \
--cc=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox