From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH] nvme-cli: bug-fix: use right file name for perror.
Date: Mon, 27 Feb 2017 16:39:58 +0200 [thread overview]
Message-ID: <89568503-d0db-9183-09ea-e3c3eabd9fd5@grimberg.me> (raw)
In-Reply-To: <1488092823-21513-1-git-send-email-chaitanya.kulkarni@hgst.com>
Looks good,
Reviewed-by: Sagi Grimberg <sagi at grimbeg.me>
next prev parent reply other threads:[~2017-02-27 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 7:07 [PATCH] nvme-cli: bug-fix: use right file name for perror Chaitanya Kulkarni
2017-02-27 14:39 ` Sagi Grimberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-12 23:13 Chaitanya Kulkarni
2017-03-12 23:13 ` Chaitanya Kulkarni
2017-03-13 16:54 ` 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=89568503-d0db-9183-09ea-e3c3eabd9fd5@grimberg.me \
--to=sagi@grimberg.me \
/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).