From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: Fix disk names when not using nvme multipath
Date: Wed, 18 Apr 2018 17:34:45 +0200 [thread overview]
Message-ID: <20180418153445.GA8513@lst.de> (raw)
In-Reply-To: <20180418153410.GM11513@localhost.localdomain>
On Wed, Apr 18, 2018@09:34:11AM -0600, Keith Busch wrote:
> I think the permissions just have to be 0444 so that the user can't change the
> naming method after some disks were named with the alternate method.
True. We should do that anyway. I'll turn this into a real series
with a few more final touches tomorrow.
next prev parent reply other threads:[~2018-04-18 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 22:03 [PATCH] nvme: Fix disk names when not using nvme multipath Keith Busch
2018-04-18 6:44 ` Christoph Hellwig
2018-04-18 13:26 ` Keith Busch
2018-04-18 15:04 ` Christoph Hellwig
2018-04-18 15:34 ` Keith Busch
2018-04-18 15:34 ` Christoph Hellwig [this message]
2018-04-18 16:09 ` Keith Busch
2018-04-19 8:50 ` Christoph Hellwig
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=20180418153445.GA8513@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 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.