From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/2] nvme: Introduce nvme_is_aen_req function
Date: Wed, 12 Dec 2018 09:10:53 +0100 [thread overview]
Message-ID: <20181212081053.GB29679@lst.de> (raw)
In-Reply-To: <1e347e83-1f06-3e43-7dfe-fe7b0e6f264f@grimberg.me>
On Tue, Dec 11, 2018@11:46:04PM -0800, Sagi Grimberg wrote:
> Don't really see the point of this wrapper... But if
> you are going to introduce it, you need to have others
> use it as well...
I have to say I kinda like the helper. But yes, we should convert
all the transports over to it.
prev parent reply other threads:[~2018-12-12 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 6:55 [PATCH 1/2] nvme: Introduce nvme_is_aen_req function Nitzan Carmi
2018-12-12 6:55 ` [PATCH 2/2] nvme-rdma: Handle completions if error_recovery fails Nitzan Carmi
2018-12-12 7:56 ` Sagi Grimberg
2018-12-12 8:12 ` Christoph Hellwig
2018-12-12 7:46 ` [PATCH 1/2] nvme: Introduce nvme_is_aen_req function Sagi Grimberg
2018-12-12 8:10 ` Christoph Hellwig [this message]
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=20181212081053.GB29679@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.