Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: james.smart@broadcom.com (James Smart)
Subject: [PATCH] nvme-pci: quiesce IO queues prior to disabling device HMB accesses
Date: Fri, 16 Feb 2018 09:42:08 -0800	[thread overview]
Message-ID: <60dcb8f0-7139-3c3e-1838-2347ce67dbcc@broadcom.com> (raw)
In-Reply-To: <22af82dd-0f20-f68b-2725-59b0da259e69@grimberg.me>

On 2/12/2018 10:40 AM, Sagi Grimberg wrote:
> Thanks, I picked this up for 4.17 (unless someone thinks
> this is 4.16-rc material?)
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme

Note: I really hope that we can eventually commonize all the 
quiesce/unquiesce logic and points relative to controller state.? We 
have just enough differences to be interesting.

-- james

      reply	other threads:[~2018-02-16 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 12:57 [PATCH] nvme-pci: quiesce IO queues prior to disabling device HMB accesses Jianchao Wang
2018-02-12 18:40 ` Sagi Grimberg
2018-02-16 17:42   ` James Smart [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=60dcb8f0-7139-3c3e-1838-2347ce67dbcc@broadcom.com \
    --to=james.smart@broadcom.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