From: krisman@linux.vnet.ibm.com (Gabriel Krisman Bertazi)
Subject: nvme_change_ctrl_state() bug?
Date: Fri, 12 Aug 2016 14:40:32 -0300 [thread overview]
Message-ID: <878tw1sx67.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <258e01d1f4be$ec094890$c41bd9b0$@opengridcomputing.com> (Steve Wise's message of "Fri, 12 Aug 2016 12:28:20 -0500")
"Steve Wise" <swise at opengridcomputing.com> writes:
> Shouldn't the assigning of the state be inside the lock?
Yes, I sent a patch for it, but it hasn't been accepted yet.
http://lists.infradead.org/pipermail/linux-nvme/2016-July/005551.html
--
Gabriel Krisman Bertazi
prev parent reply other threads:[~2016-08-12 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 17:28 nvme_change_ctrl_state() bug? Steve Wise
2016-08-12 17:40 ` Gabriel Krisman Bertazi [this message]
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=878tw1sx67.fsf@linux.vnet.ibm.com \
--to=krisman@linux.vnet.ibm.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).