From: Andy Lutomirski <luto@kernel.org>
To: linux-nvme@lists.infradead.org
Cc: Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 0/4] systemd ID improvements
Date: Thu, 19 Dec 2019 19:31:01 -0800 [thread overview]
Message-ID: <cover.1576726427.git.luto@kernel.org> (raw)
Hi all-
This was github PR #594, but Keith asked me to email it.
Please review this carefully. Also, if you merge this, please
consider changing the 'luto.us' bit to something a bit more
sensible. Maybe com.github.linux-nvme?
I'm still dubious about the way that newlines in the ids are
handled, but my patches don't change that per se.
Andy Lutomirski (4):
hostnqn: Fix the systemd-based NQN namespace to comply with the spec
fabrics: Rename nvmf_hostnqn_file() to nvmf_hostnqn_load()
Use systemd-generated hostid if no hostid is configured
Do not install /etc/nvme/hostid or /etc/nvme/hostnqn by default
Documentation/nvme-show-hostid.txt | 29 +++++++++++++
Makefile | 4 +-
fabrics.c | 68 +++++++++++++++++++++++++-----
fabrics.h | 1 +
nvme-builtin.h | 1 +
nvme.c | 15 +++++++
6 files changed, 105 insertions(+), 13 deletions(-)
create mode 100644 Documentation/nvme-show-hostid.txt
--
2.23.0
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2019-12-20 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 3:31 Andy Lutomirski [this message]
2019-12-20 3:31 ` [PATCH 1/4] hostnqn: Fix the systemd-based NQN namespace to comply with the spec Andy Lutomirski
2019-12-20 3:31 ` [PATCH 2/4] fabrics: Rename nvmf_hostnqn_file() to nvmf_hostnqn_load() Andy Lutomirski
2019-12-20 3:31 ` [PATCH 3/4] Use systemd-generated hostid if no hostid is configured Andy Lutomirski
2020-01-03 18:14 ` David Milburn
2020-01-13 19:14 ` Andy Lutomirski
2019-12-20 3:31 ` [PATCH 4/4] Do not install /etc/nvme/hostid or /etc/nvme/hostnqn by default Andy Lutomirski
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=cover.1576726427.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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.