From: keith.busch@linux.intel.com (Keith Busch)
Subject: [PATCH] nvme-cli: Fix the displayed metadata length value on Big Endian systems.
Date: Fri, 24 Aug 2018 13:11:06 -0600 [thread overview]
Message-ID: <20180824191106.GA26522@localhost.localdomain> (raw)
In-Reply-To: <1535135667-32608-1-git-send-email-jeff.lien@wdc.com>
On Fri, Aug 24, 2018@01:34:27PM -0500, Jeff Lien wrote:
> On BE systems, the metadata length value displayed as part of the
> format in the nvme list command is byte swapped. So a value of 0
> appears just fine but a value of 8 bytes is displayed as 0x0800.
> This patch fixes that is the value is correct for both LE and BE
> systems.
>
> Signed-off-by: Jeff Lien <jeff.lien at wdc.com>
Thanks, applied.
prev parent reply other threads:[~2018-08-24 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 18:34 [PATCH] nvme-cli: Fix the displayed metadata length value on Big Endian systems Jeff Lien
2018-08-24 19:11 ` Keith Busch [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=20180824191106.GA26522@localhost.localdomain \
--to=keith.busch@linux.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