From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] NVMe: Export NVMe attributes to sysfs group
Date: Tue, 8 Dec 2015 00:00:29 +0000 [thread overview]
Message-ID: <20151208000029.GC31067@localhost.localdomain> (raw)
In-Reply-To: <20151207233112.GB26585@infradead.org>
On Mon, Dec 07, 2015@03:31:12PM -0800, Christoph Hellwig wrote:
> We really need to expose the NGUID on the namespace at the same time.
> Otherwise people will use this information to incorrectly provide a
> serial number of the block devices in udev because not better
> information is available.
I'm planning to tackle that next. NGUID can not be in the same attribute
group. It needs to be in a new namespace group instead.
Right now all I got is the NGUID/EUI64. Any opinion on what to name the
attribute? I was going with "id". The systemd developers didn't provide
a very strong opinion, and I think they were confusing "serial" as a
unique identifier.
While I'm in this area, are there other namespace attributes anyone is
interested in exposing?
next prev parent reply other threads:[~2015-12-08 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 23:20 [PATCH] NVMe: Export NVMe attributes to sysfs group Keith Busch
2015-12-07 23:31 ` Christoph Hellwig
2015-12-08 0:00 ` Keith Busch [this message]
2015-12-09 18:33 ` 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=20151208000029.GC31067@localhost.localdomain \
--to=keith.busch@intel.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