From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 1/2] nvme-rdma: Allow DELETING state change failure in error_recovery
Date: Tue, 20 Mar 2018 13:30:50 +0200 [thread overview]
Message-ID: <ef6711a4-cfdb-d38a-0a81-e20dcb463e98@grimberg.me> (raw)
In-Reply-To: <20180320110730.24070-1-nitzanc@mellanox.com>
Looks good,
Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
next prev parent reply other threads:[~2018-03-20 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 11:07 [PATCH 1/2] nvme-rdma: Allow DELETING state change failure in error_recovery Nitzan Carmi
2018-03-20 11:07 ` [PATCH 2/2] nvme: Add .stop_ctrl to nvme ctrl ops Nitzan Carmi
2018-03-20 11:30 ` Sagi Grimberg [this message]
2018-03-20 22:11 ` [PATCH 1/2] nvme-rdma: Allow DELETING state change failure in error_recovery 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=ef6711a4-cfdb-d38a-0a81-e20dcb463e98@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