From: hch@lst.de (Christoph Hellwig)
Subject: nvme defintions not used in the kernel
Date: Thu, 29 Jun 2017 01:11:29 +0200 [thread overview]
Message-ID: <20170628231129.GA20902@lst.de> (raw)
Hi all,
currently nvme-cli supports various nvme features that are not
needed in the kernel and keeps them in its own nvme.h file,
in addition to pulling in the kernel one.
Do we want to keep it that way in the long run, or just add
things to nvme.h in the kernel even if they are not used to
keep things in a single place.
To me the latter would seem a little nicer, especially as it
doesn't involve a whole lot of defintion.
next reply other threads:[~2017-06-28 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 23:11 Christoph Hellwig [this message]
2017-06-28 23:13 ` nvme defintions not used in the kernel Jens Axboe
2017-06-29 5:44 ` Sagi Grimberg
2017-06-29 8:32 ` Johannes Thumshirn
2017-06-29 13:31 ` Christoph Hellwig
2017-06-29 14:25 ` Sagi Grimberg
2017-06-29 15:37 ` 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=20170628231129.GA20902@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