From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 2/2] nvme: Use CNS as 8-bit field and avoid endianness conversion
Date: Thu, 26 Jan 2017 12:09:16 -0500 [thread overview]
Message-ID: <20170126170916.GB1048@localhost.localdomain> (raw)
In-Reply-To: <1485443848-29478-2-git-send-email-maxg@mellanox.com>
On Thu, Jan 26, 2017@05:17:28PM +0200, Max Gurtovoy wrote:
> From: Parav Pandit <parav at mellanox.com>
>
> This patch defines CNS field as 8-bit field and avoids cpu_to/from_le
> conversions.
> Also initialize nvme_command cns value explicitly to NVME_ID_CNS_NS
> for readability (don't rely on the fact that NVME_ID_CNS_NS = 0).
>
> Reviewed-by: Max Gurtovoy <maxg at mellanox.com>
> Signed-off-by: Parav Pandit <parav at mellanox.com>
Reviewed-by: Keith Busch <keith.busch at intel.com>
next prev parent reply other threads:[~2017-01-26 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 15:17 [PATCH 1/2] nvme: add semicolon in nvme_command setting Max Gurtovoy
2017-01-26 15:17 ` [PATCH 2/2] nvme: Use CNS as 8-bit field and avoid endianness conversion Max Gurtovoy
2017-01-26 17:09 ` Keith Busch [this message]
2017-01-26 17:08 ` [PATCH 1/2] nvme: add semicolon in nvme_command setting 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=20170126170916.GB1048@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