From: hch@lst.de (Christoph Hellwig)
Subject: nvme-cli: finish the move of vendor specific commands to plugins
Date: Mon, 13 Mar 2017 17:10:50 -0600 [thread overview]
Message-ID: <20170313231054.30400-1-hch@lst.de> (raw)
Move the remaining Intel specific support code from the core to the
Intel plugin.
next reply other threads:[~2017-03-13 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 23:10 Christoph Hellwig [this message]
2017-03-13 23:10 ` [PATCH 1/4] move show_intel_smart_log to intel-nvme.c Christoph Hellwig
2017-03-13 23:10 ` [PATCH 2/4] remove json_add_smart_log Christoph Hellwig
2017-03-13 23:10 ` [PATCH 3/4] remove nvme_intel_smart_log Christoph Hellwig
2017-03-13 23:10 ` [PATCH 4/4] move struct nvme_additional_smart_log to intel-nvme.c Christoph Hellwig
2017-03-14 15:02 ` nvme-cli: finish the move of vendor specific commands to plugins Keith Busch
2017-03-19 22:46 ` Sagi Grimberg
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=20170313231054.30400-1-hch@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;
as well as URLs for NNTP newsgroup(s).