From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 3/3] nvme-cli: fix header paths for new structure
Date: Mon, 29 Oct 2018 16:02:11 -0600 [thread overview]
Message-ID: <20181029220211.GA17365@localhost.localdomain> (raw)
In-Reply-To: <BYAPR04MB4502A2FF67025B4D4C67103186F30@BYAPR04MB4502.namprd04.prod.outlook.com>
On Mon, Oct 29, 2018@09:45:18PM +0000, Chaitanya Kulkarni wrote:
> Can we get patch 1 and 2 in ? maybe we can drop 3rd one.
Done.
prev parent reply other threads:[~2018-10-29 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 17:08 [PATCH 1/3] nvme-cli: fix array len to hold string of size 4 Chaitanya Kulkarni
2018-10-26 17:08 ` [PATCH 2/3] nvme-cli: fix endianness for the structure field Chaitanya Kulkarni
2018-10-26 17:08 ` [PATCH 3/3] nvme-cli: fix header paths for new structure Chaitanya Kulkarni
2018-10-26 20:07 ` Keith Busch
2018-10-26 20:11 ` Chaitanya Kulkarni
2018-10-26 20:17 ` Keith Busch
2018-10-26 21:56 ` Chaitanya Kulkarni
2018-10-29 21:45 ` Chaitanya Kulkarni
2018-10-29 22:02 ` 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=20181029220211.GA17365@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