From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH] nvme: add a constant for the identify payload size
Date: Thu, 10 Mar 2016 09:26:12 +0100 [thread overview]
Message-ID: <20160310082612.GH3464@c203.arch.suse.de> (raw)
In-Reply-To: <1457542477-25191-1-git-send-email-hch@lst.de>
On Wed, Mar 09, 2016@05:54:37PM +0100, Christoph Hellwig wrote:
> The NVMe spec specifies a hardcoded payload length of 4k for all
> types of Identify commands. Use a constant instead of hardcoded
> values that can be confused for the page size.
>
> Signed-off-by: Christoph Hellwig <hch at lst.de>
Reviewed-by: Johannes Thumshirn <jthumshirn at suse.de>
--
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
prev parent reply other threads:[~2016-03-10 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 16:54 [PATCH] nvme: add a constant for the identify payload size Christoph Hellwig
2016-03-09 16:57 ` Sagi Grimberg
2016-03-09 19:07 ` Matthew Wilcox
2016-03-10 8:06 ` Christoph Hellwig
2016-03-10 14:30 ` Matthew Wilcox
2016-03-10 8:27 ` Johannes Thumshirn
2016-03-10 8:26 ` Johannes Thumshirn [this message]
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=20160310082612.GH3464@c203.arch.suse.de \
--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