From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: Add tertiary number to NVME_VS
Date: Wed, 21 Sep 2016 13:12:10 -0700 [thread overview]
Message-ID: <20160921201210.GA29507@infradead.org> (raw)
In-Reply-To: <1474488352-20601-1-git-send-email-krisman@linux.vnet.ibm.com>
On Wed, Sep 21, 2016@05:05:52PM -0300, Gabriel Krisman Bertazi wrote:
> NVMe 1.2.1 specification adds a tertiary element to the version number.
> This updates the macro and its callers to include the final number and
> fixup a single place in nvmet where the version was generated manually.
>
> For versions prior to 1.2.1, which didn't have the tertiary number, it's
> ok to assume the last number as zero, because that bit would be
> reserved, and the specification defines reserved bits as 0.
Nice cleanups, thanks a lot!
Reviewed-by: Christoph Hellwig <hch at lst.de>
next prev parent reply other threads:[~2016-09-21 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 20:05 [PATCH] nvme: Add tertiary number to NVME_VS Gabriel Krisman Bertazi
2016-09-21 20:12 ` Christoph Hellwig [this message]
2016-09-21 20:12 ` Sagi Grimberg
2016-10-04 18:40 ` Gabriel Krisman Bertazi
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=20160921201210.GA29507@infradead.org \
--to=hch@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 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).