From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme-cli: bug-fix: use right file name for perror.
Date: Mon, 13 Mar 2017 12:54:40 -0400 [thread overview]
Message-ID: <20170313165439.GA25758@localhost.localdomain> (raw)
In-Reply-To: <1489360404-16256-2-git-send-email-chaitanya.kulkarni@hgst.com>
On Sun, Mar 12, 2017@04:13:24PM -0700, Chaitanya Kulkarni wrote:
> Use right file descriptor while printing an error, when
> --metadata option is used for read/write commands.
>
> Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni at hgst.com>
Applied, thanks for the fix.
next prev parent reply other threads:[~2017-03-13 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 23:13 [PATCH] nvme-cli: bug-fix: use right file name for perror Chaitanya Kulkarni
2017-03-12 23:13 ` Chaitanya Kulkarni
2017-03-13 16:54 ` Keith Busch [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-26 7:07 Chaitanya Kulkarni
2017-02-27 14:39 ` Sagi Grimberg
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=20170313165439.GA25758@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;
as well as URLs for NNTP newsgroup(s).