From: james.smart@broadcom.com (James Smart)
Subject: [PATCH v2] nvmet_fc: support target port removal with nvmet layer
Date: Tue, 11 Sep 2018 10:01:50 -0700 [thread overview]
Message-ID: <0d9183ca-6ec6-4477-c954-bc29d66e5b0c@broadcom.com> (raw)
In-Reply-To: <20180911073514.GB12254@infradead.org>
On 9/11/2018 12:35 AM, Christoph Hellwig wrote:
> Thanks,
>
> applied to nvme-4.20.
thanks
prev parent reply other threads:[~2018-09-11 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 23:48 [PATCH v2] nvmet_fc: support target port removal with nvmet layer James Smart
2018-08-10 17:53 ` Ewan D. Milne
2018-08-10 23:21 ` James Smart
2018-08-13 16:38 ` Ewan D. Milne
2018-08-10 20:50 ` Ewan D. Milne
2018-08-10 23:04 ` James Smart
2018-09-05 19:56 ` Christoph Hellwig
2018-09-05 20:12 ` James Smart
2018-09-11 7:17 ` Christoph Hellwig
2018-09-05 20:24 ` Ewan D. Milne
2018-09-05 20:40 ` James Smart
2018-09-11 7:35 ` Christoph Hellwig
2018-09-11 17:01 ` James Smart [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=0d9183ca-6ec6-4477-c954-bc29d66e5b0c@broadcom.com \
--to=james.smart@broadcom.com \
/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).