From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme-fc: fix request private initialization
Date: Thu, 1 Nov 2018 07:09:48 +0100 [thread overview]
Message-ID: <20181101060948.GA4999@lst.de> (raw)
In-Reply-To: <20181027194154.3965-1-jsmart2021@gmail.com>
Thanks,
applied to nvme-4.20.
prev parent reply other threads:[~2018-11-01 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 19:41 [PATCH] nvme-fc: fix request private initialization James Smart
2018-10-30 19:45 ` Sagi Grimberg
2018-11-01 6:09 ` 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=20181101060948.GA4999@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;
as well as URLs for NNTP newsgroup(s).