Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bart.VanAssche@sandisk.com (Bart Van Assche)
Subject: hch's native NVMe multipathing [was: Re: [PATCH 1/2] Don't blacklist nvme]
Date: Thu, 16 Feb 2017 20:58:13 +0000	[thread overview]
Message-ID: <1487278678.2612.6.camel@sandisk.com> (raw)
In-Reply-To: <20170216202339.GB13742@redhat.com>

On Thu, 2017-02-16@15:23 -0500, Mike Snitzer wrote:
> Or you can wait to rebase on v4.11-rc1 in ~2 weeks.

Hello Mike,

I will wait until v4.11-rc1 has been released.

Thanks,

Bart.

  reply	other threads:[~2017-02-16 20:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1487107154-24883-1-git-send-email-keith.busch@intel.com>
     [not found] ` <20170215145617.GA4241@infradead.org>
2017-02-16  2:53   ` hch's native NVMe multipathing [was: Re: [PATCH 1/2] Don't blacklist nvme] Mike Snitzer
2017-02-16  5:00     ` [dm-devel] " Bart Van Assche
2017-02-16 12:37       ` Mike Snitzer
2017-02-16 19:46         ` Bart Van Assche
2017-02-16 20:23           ` Mike Snitzer
2017-02-16 20:58             ` Bart Van Assche [this message]
2017-02-16 14:26     ` [dm-devel] " Christoph Hellwig
2017-02-16 15:13       ` Mike Snitzer
2017-02-16 17:38         ` Keith Busch
2017-02-16 17:37           ` Bart Van Assche
2017-02-16 18:07             ` Keith Busch
2017-02-16 18:21               ` Mike Snitzer
2017-02-16 20:40                 ` Keith Busch
2017-02-17  9:04                 ` [dm-devel] " hch
2017-02-17 14:43                   ` Mike Snitzer
2017-02-16 18:05         ` Sagi Grimberg
2017-02-17  9:05           ` [dm-devel] " Christoph Hellwig
2017-02-17 14:37             ` Mike Snitzer
2017-02-17  9:33         ` [dm-devel] " Christoph Hellwig
2017-02-17 14:32           ` Mike Snitzer

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=1487278678.2612.6.camel@sandisk.com \
    --to=bart.vanassche@sandisk.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