All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: linux-nvme@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH-stable] nvme: protect against simultaneous shutdown invocations
Date: Fri, 6 Oct 2017 09:09:13 -0600	[thread overview]
Message-ID: <20171006150912.GA17569@localhost.localdomain> (raw)
In-Reply-To: <20171006150557.17492-1-keith.busch@intel.com>

On Fri, Oct 06, 2017 at 09:05:57AM -0600, Keith Busch wrote:
> commit 77bf25ea70200cddf083f74b7f617e5f07fac8bd upstream
> 
> Back-ported to 4.4. The only difference is the file location of the
> struct definition that's adding the mutex.

Err, sorry, please disregard this one. There is a mistake in the back
port that will break. Will send out the correct version.

WARNING: multiple messages have this Message-ID (diff)
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH-stable] nvme: protect against simultaneous shutdown invocations
Date: Fri, 6 Oct 2017 09:09:13 -0600	[thread overview]
Message-ID: <20171006150912.GA17569@localhost.localdomain> (raw)
In-Reply-To: <20171006150557.17492-1-keith.busch@intel.com>

On Fri, Oct 06, 2017@09:05:57AM -0600, Keith Busch wrote:
> commit 77bf25ea70200cddf083f74b7f617e5f07fac8bd upstream
> 
> Back-ported to 4.4. The only difference is the file location of the
> struct definition that's adding the mutex.

Err, sorry, please disregard this one. There is a mistake in the back
port that will break. Will send out the correct version.

  reply	other threads:[~2017-10-06 15:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 15:05 [PATCH-stable] nvme: protect against simultaneous shutdown invocations Keith Busch
2017-10-06 15:05 ` Keith Busch
2017-10-06 15:09 ` Keith Busch [this message]
2017-10-06 15:09   ` Keith Busch
2017-10-06 15:14 Keith Busch
2017-10-06 15:14 ` Keith Busch
2017-10-10 17:47 ` Greg KH
2017-10-10 17:47   ` Greg KH

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=20171006150912.GA17569@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=linux-nvme@lists.infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.