From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme/pci: Don't free queues on error
Date: Wed, 16 Nov 2016 13:46:07 -0500 [thread overview]
Message-ID: <20161116184607.GC10050@localhost.localdomain> (raw)
In-Reply-To: <20161116170855.GB5005@lst.de>
On Wed, Nov 16, 2016@06:08:55PM +0100, Christoph Hellwig wrote:
> should this get a Cc to stable?
Sure thing, but it'll have be a different patch going back to just
stable-4.8.y. I'll follow "option 3" from the Stable Kernel Rules once
this is applied.
next prev parent reply other threads:[~2016-11-16 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 20:56 [PATCH] nvme/pci: Don't free queues on error Keith Busch
2016-11-16 16:48 ` Sagi Grimberg
2016-11-16 17:08 ` Christoph Hellwig
2016-11-16 18:46 ` Keith Busch [this message]
2016-11-16 19:40 ` Jens Axboe
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=20161116184607.GC10050@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;
as well as URLs for NNTP newsgroup(s).