From: Scott Bauer <scott.bauer@intel.com>
To: Jens Axboe <axboe@fb.com>
Cc: Christoph Hellwig <hch@lst.de>,
Jon Derrick <jonathan.derrick@intel.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Rafael Antognolli <rafael.antognolli@intel.com>
Subject: Re: [PATCHv4 4/4] block/sed: Embed function data into the function sequence
Date: Wed, 22 Feb 2017 09:13:31 -0700 [thread overview]
Message-ID: <20170222161331.GA2696@sbauer-Z170X-UD5> (raw)
In-Reply-To: <22a94611-3cbd-792f-8347-3b1c1f200944@fb.com>
On Wed, Feb 22, 2017 at 09:10:31AM -0700, Jens Axboe wrote:
> On 02/22/2017 12:13 AM, Christoph Hellwig wrote:
> >> + if (!lock_held)
> >> + mutex_lock(&dev->dev_lock);
> >
> > No conditional locking, please. I guess I causesd this by asking you
> > to remove __opal_lock_unlock, but it seems we'd either need to keep it
> > in the end.
> >
> > Except for that the series looks fine to me.
> >
> > Jens: given that 1-3 are the important fixes how about you pick those
> > up ASAP? They all also had my Reviewed-by for previous postings.
>
> I picked up 1-3, and re-added your reviewed by. #4 should be sorted
> before -rc1, though.
>
#4 Is good to go as well. It was resent this morning under
[PATCH] block/sed: Embed function data into the function sequence
And contains the changes Christoph requested, I'll re-add my sign-off.
Once that gets In I can rebase mine and get them out today too.
next prev parent reply other threads:[~2017-02-22 16:23 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 [this message]
2017-02-22 16:47 ` Jens Axboe
2017-02-22 17:22 ` Keith Busch
2017-02-22 2:42 ` [PATCHv4 0/4] OPAL patches, cont'd Jens Axboe
2017-02-22 3:14 ` 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=20170222161331.GA2696@sbauer-Z170X-UD5 \
--to=scott.bauer@intel.com \
--cc=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 \
/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