From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v4 1/3] nvme: Introduce NVMe 1.4 Identify Namespace fields in struct nvme_id_ns
Date: Fri, 28 Jun 2019 09:00:38 +0200 [thread overview]
Message-ID: <20190628070038.GA28268@lst.de> (raw)
In-Reply-To: <20190627143215.27443-2-bvanassche@acm.org>
On Thu, Jun 27, 2019@07:32:13AM -0700, Bart Van Assche wrote:
> Several new fields have been introduced in version 1.4 of the NVMe spec
> at offsets that were defined as reserved in version 1.3d of the NVMe
> spec. Update the definition of the nvme_id_ns data structure such that
> it is in sync with version 1.4 of the NVMe spec. This change preserves
> backwards compatibility.
>
> Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni at wdc.com>
> Reviewed-by: Martin K. Petersen <martin.petersen at oracle.com>
> Reviewed-by: Keith Busch <kbusch at kernel.org>
> Cc: Sagi Grimberg <sagi at grimberg.me>
> Cc: Hannes Reinecke <hare at suse.com>
> Signed-off-by: Bart Van Assche <bvanassche at acm.org>
Looks good:
Reviewed-by: Christoph Hellwig <hch at lst.de>
next prev parent reply other threads:[~2019-06-28 7:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 14:32 [PATCH v4 0/3] NVMe 1.4 Identify Namespace Support Bart Van Assche
2019-06-27 14:32 ` [PATCH v4 1/3] nvme: Introduce NVMe 1.4 Identify Namespace fields in struct nvme_id_ns Bart Van Assche
2019-06-28 7:00 ` Christoph Hellwig [this message]
2019-06-27 14:32 ` [PATCH v4 2/3] nvmet: Export NVMe namespace attributes Bart Van Assche
2019-06-27 17:11 ` Chaitanya Kulkarni
2019-06-28 7:02 ` Christoph Hellwig
2019-06-27 14:32 ` [PATCH v4 3/3] nvme: Set physical block size and optimal I/O size according to NVMe 1.4 Bart Van Assche
2019-06-28 7:06 ` Christoph Hellwig
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=20190628070038.GA28268@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