From: keith.busch@intel.com (Keith Busch)
Subject: nvme-4.14 rebased
Date: Wed, 16 Aug 2017 12:07:14 -0400 [thread overview]
Message-ID: <20170816160714.GK7233@localhost.localdomain> (raw)
In-Reply-To: <fe7dede5-824f-fc20-766d-417775193c66@intel.com>
On Fri, Aug 11, 2017@05:08:37AM -0600, Jon Derrick wrote:
> On 08/16/2017 02:13 AM, Christoph Hellwig wrote:
> > Hi all,
> >
> > I've rebased the nvme-4.14 branch on top of the nvme-4.13 branch
> > to avoid conflicts. As part of that I made the timestamp set features
> > return an error similar to the other reset fixes.
> >
> > Jon: can you double check the change is correct?
> >
>
> Hi Christoph,
>
> The only thing I'd suggest is not letting a failure to set the timestamp
> be a failure to initialize the controller.
It looks like Christoph just has it fail initialization if the timestamp
feature command never gets a controller response. We actually do need
to abandon controller init in that case since the controller is disabled
in the timeout handler.
prev parent reply other threads:[~2017-08-16 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 8:13 nvme-4.14 rebased Christoph Hellwig
2017-08-11 11:08 ` Jon Derrick
2017-08-16 16:07 ` Keith Busch [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=20170816160714.GK7233@localhost.localdomain \
--to=keith.busch@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