From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 1/3] nvme: fix the dangerous reference of namespaces list
Date: Mon, 12 Feb 2018 20:46:10 +0200 [thread overview]
Message-ID: <4837ee1c-da12-e315-5c46-22d05aa66bee@grimberg.me> (raw)
In-Reply-To: <1518440086-583-1-git-send-email-jianchao.w.wang@oracle.com>
Looks good,
Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
next prev parent reply other threads:[~2018-02-12 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 12:54 [PATCH 1/3] nvme: fix the dangerous reference of namespaces list Jianchao Wang
2018-02-12 12:54 ` [PATCH 2/3] nvme: fix the deadlock in nvme_update_formats Jianchao Wang
2018-02-12 18:46 ` Sagi Grimberg
2018-02-12 19:20 ` Keith Busch
2018-02-12 20:25 ` Keith Busch
2018-02-12 12:54 ` [PATCH 3/3] nvme: change namespaces_mutext to namespaces_rwsem Jianchao Wang
2018-02-12 18:47 ` Sagi Grimberg
2018-02-12 19:30 ` Keith Busch
2018-02-12 18:46 ` Sagi Grimberg [this message]
2018-02-12 19:29 ` [PATCH 1/3] nvme: fix the dangerous reference of namespaces list Keith Busch
2018-02-12 19:37 ` 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=4837ee1c-da12-e315-5c46-22d05aa66bee@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