From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvmet-fc: Bring Disconnect into compliance with FC-NVME spec
Date: Tue, 12 Mar 2019 12:31:03 -0700 [thread overview]
Message-ID: <20190312193103.GB22751@infradead.org> (raw)
In-Reply-To: <20190205173902.17947-1-jsmart2021@gmail.com>
Thanks,
applied to nvme-5.1.
prev parent reply other threads:[~2019-03-12 19:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 17:39 [PATCH] nvmet-fc: Bring Disconnect into compliance with FC-NVME spec James Smart
2019-02-06 13:44 ` Ewan D. Milne
[not found] ` <20190220221454.GA31450@osmithde-lnx.cisco.com>
2019-02-21 17:35 ` Oliver Smith-Denny
2019-02-21 18:29 ` James Smart
2019-02-21 18:45 ` Oliver Smith-Denny
2019-02-21 23:16 ` Oliver Smith-Denny
2019-02-26 21:53 ` James Smart
2019-02-27 20:25 ` Oliver Smith-Denny
2019-02-28 22:47 ` Oliver Smith-Denny
2019-03-12 19:31 ` 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=20190312193103.GB22751@infradead.org \
--to=hch@infradead.org \
/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