From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: nvme defintions not used in the kernel
Date: Thu, 29 Jun 2017 10:32:28 +0200 [thread overview]
Message-ID: <20170629083228.GE3808@linux-x5ow.site> (raw)
In-Reply-To: <6503552c-afac-b740-5db6-31d4a7e34256@grimberg.me>
On Thu, Jun 29, 2017@08:44:04AM +0300, Sagi Grimberg wrote:
> I agree with the latter, should we also move nvme.h to
> uapi?
That was my first reaction as well. I'm all for it.
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2017-06-29 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 23:11 nvme defintions not used in the kernel Christoph Hellwig
2017-06-28 23:13 ` Jens Axboe
2017-06-29 5:44 ` Sagi Grimberg
2017-06-29 8:32 ` Johannes Thumshirn [this message]
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=20170629083228.GE3808@linux-x5ow.site \
--to=jthumshirn@suse.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