From: Keith Busch <keith.busch@intel.com>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>
Cc: "Machalow, Charles" <charles.machalow@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] Fix controller reset return
Date: Fri, 11 May 2018 10:36:53 -0600 [thread overview]
Message-ID: <20180511163653.GA7322@localhost.localdomain> (raw)
In-Reply-To: <20180511162501.7258-1-keith.busch@intel.com>
I'll just need to append "nvme:" to the front of the changelog subject,
otherwise I think this is a trivial fix.
For future, there are multiple places that look for LIVE and ADMIN_ONLY,
so might be worth refactoring this into a function later.
next prev parent reply other threads:[~2018-05-11 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 16:25 [PATCH] Fix controller reset return Keith Busch
2018-05-11 16:36 ` Keith Busch [this message]
2018-05-25 9:10 ` Christoph Hellwig
2018-05-25 14:50 ` Keith Busch
2018-05-25 14:55 ` 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=20180511163653.GA7322@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=charles.machalow@intel.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
/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).