From: vishal.l.verma@intel.com (Verma, Vishal L)
Subject: [PATCHv2] NVMe: Use last bytes of f/w rev SCSI Inquiry
Date: Tue, 6 May 2014 15:29:05 +0000 [thread overview]
Message-ID: <1399390114.4085.1.camel@omniknight.lm.intel.com> (raw)
In-Reply-To: <1398808347-9839-1-git-send-email-keith.busch@intel.com>
On Tue, 2014-04-29@15:52 -0600, Keith Busch wrote:
> After skipping right-padded spaces, use the last four bytes of the
> firmware revision when reporting the Inquiry Product Revision. These
> are generally more indicative to what is running.
>
> Signed-off-by: Keith Busch <keith.busch at intel.com>
> ---
Looks good!
Acked-by: Vishal Verma <vishal.l.verma at linux.intel.com>
prev parent reply other threads:[~2014-05-06 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 21:52 [PATCHv2] NVMe: Use last bytes of f/w rev SCSI Inquiry Keith Busch
2014-05-06 15:29 ` Verma, Vishal L [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=1399390114.4085.1.camel@omniknight.lm.intel.com \
--to=vishal.l.verma@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