From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/2] nvme/multipath: Disable runtime writable enabling parameter
Date: Wed, 31 Oct 2018 06:28:38 +0100 [thread overview]
Message-ID: <20181031052838.GB13521@lst.de> (raw)
In-Reply-To: <20181030182455.GA19483@localhost.localdomain>
On Tue, Oct 30, 2018@12:24:56PM -0600, Keith Busch wrote:
> Everything on the nvme mailing list is out of whack for me. It looks
> like lists.infradead.org is toast. I can still ssh to git.infradead.org,
> but can't access its gitweb.
Even the mail part didn't work yesterday Israeli time, so it might just
take some more time to be back up.
next prev parent reply other threads:[~2018-10-31 5:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 21:49 [PATCH 0/2] nvme multipath naming fixes Keith Busch
2018-04-26 21:49 ` [PATCH 1/2] nvme/multipath: Disable runtime writable enabling parameter Keith Busch
2018-04-27 5:20 ` Christoph Hellwig
2018-04-27 15:48 ` Keith Busch
2018-10-30 18:17 ` Sagi Grimberg
2018-10-30 18:18 ` Sagi Grimberg
2018-10-30 18:24 ` Keith Busch
2018-10-31 5:28 ` Christoph Hellwig [this message]
2018-04-26 21:49 ` [PATCH 2/2] nvme/multipath: Fix multipath disabled naming collisions Keith Busch
2018-04-27 5:21 ` Christoph Hellwig
2018-10-29 15:37 ` Stephen Bates
2018-10-29 15:42 ` Keith Busch
2018-10-29 15:48 ` Stephen Bates
2018-10-29 15:55 ` Keith Busch
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=20181031052838.GB13521@lst.de \
--to=hch@lst.de \
/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