From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: Fix known effects
Date: Tue, 21 May 2019 08:49:22 +0200 [thread overview]
Message-ID: <20190521064922.GE30402@lst.de> (raw)
In-Reply-To: <20190517161346.25102-1-keith.busch@intel.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch at lst.de>
next prev parent reply other threads:[~2019-05-21 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190517161939epcas5p2993c25cc84f606cfa595cecd73698c25@epcms2p3>
2019-05-17 16:13 ` [PATCH] nvme: Fix known effects Keith Busch
2019-05-17 17:28 ` Edmund Nadolski
2019-05-17 17:32 ` Chaitanya Kulkarni
2019-05-21 6:49 ` Christoph Hellwig [this message]
2019-05-21 7:26 ` Minwoo Im
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=20190521064922.GE30402@lst.de \
--to=hch@lst.de \
/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