From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 3/5] nvme.h: add an enum for cns values
Date: Fri, 30 Sep 2016 11:19:13 -0400 [thread overview]
Message-ID: <20160930151913.GB22601@localhost.localdomain> (raw)
In-Reply-To: <1475236270-18329-4-git-send-email-hch@lst.de>
On Fri, Sep 30, 2016@01:51:08PM +0200, Christoph Hellwig wrote:
> Ported over from nvme-cli.
>
> Signed-off-by: Christoph Hellwig <hch at lst.de>
Looks good.
Reviewed-by: Keith Busch <keith.busch at intel.com>
> ---
> include/linux/nvme.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/include/linux/nvme.h b/include/linux/nvme.h
> index 30a4c00..f7b3e35 100644
> --- a/include/linux/nvme.h
> +++ b/include/linux/nvme.h
> @@ -282,6 +282,16 @@ struct nvme_id_ns {
> };
>
> enum {
> + NVME_ID_CNS_NS = 0x00,
> + NVME_ID_CNS_CTRL = 0x01,
> + NVME_ID_CNS_NS_ACTIVE_LIST = 0x02,
> + NVME_ID_CNS_NS_PRESENT_LIST = 0x10,
> + NVME_ID_CNS_NS_PRESENT = 0x11,
> + NVME_ID_CNS_CTRL_NS_LIST = 0x12,
> + NVME_ID_CNS_CTRL_LIST = 0x13,
> +};
> +
> +enum {
> NVME_NS_FEAT_THIN = 1 << 0,
> NVME_NS_FLBAS_LBA_MASK = 0xf,
> NVME_NS_FLBAS_META_EXT = 0x10,
> --
> 2.1.4
next prev parent reply other threads:[~2016-09-30 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 11:51 nvme header updates Christoph Hellwig
2016-09-30 11:51 ` [PATCH 1/5] nvme.h: resync with nvme-cli Christoph Hellwig
2016-09-30 11:51 ` [PATCH 2/5] nvme.h: don't use uuid_be Christoph Hellwig
2016-10-03 16:10 ` J Freyensee
2016-09-30 11:51 ` [PATCH 3/5] nvme.h: add an enum for cns values Christoph Hellwig
2016-09-30 15:19 ` Keith Busch [this message]
2016-09-30 11:51 ` [PATCH 4/5] nvme: use symbolic constants for CNS values Christoph Hellwig
2016-09-30 15:20 ` Keith Busch
2016-09-30 11:51 ` [PATCH 5/5] nvmet: " Christoph Hellwig
2016-10-03 16:09 ` J Freyensee
2016-09-30 13:07 ` nvme header updates Gabriel Krisman Bertazi
2016-10-19 16:53 ` Christoph Hellwig
2016-10-19 17:01 ` Jens Axboe
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=20160930151913.GB22601@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