From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme-cli: fix a typo
Date: Thu, 8 Nov 2018 07:48:56 -0700 [thread overview]
Message-ID: <20181108144855.GC15857@localhost.localdomain> (raw)
In-Reply-To: <1541683397-10260-1-git-send-email-lijie34@huawei.com>
On Thu, Nov 08, 2018@09:23:17PM +0800, lijie wrote:
> This patch fixes a typo in nvme-cli usage text.
Applied, but please make sure to include your Signed-off-by tag next time.
next prev parent reply other threads:[~2018-11-08 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 13:23 [PATCH] nvme-cli: fix a typo lijie
2018-11-08 14:48 ` Keith Busch [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-23 15:13 [PATCH ] " Rami Rosen
2018-10-29 15:26 ` Keith Busch
2018-10-05 16:57 [PATCH] " Rami Rosen
2018-10-05 20:24 ` Sagi Grimberg
2018-10-05 20:36 ` 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=20181108144855.GC15857@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