From: jsmart2021@gmail.com (jsmart2021@gmail.com)
Subject: [PATCH 5/5] nvmet_fc: add missing reference in add_port
Date: Thu, 23 Mar 2017 20:43:21 -0700 [thread overview]
Message-ID: <20170324034321.8719-6-jsmart2021@gmail.com> (raw)
In-Reply-To: <20170324034321.8719-1-jsmart2021@gmail.com>
From: James Smart <jsmart2021@gmail.com>
Add missing reference in add_port
Signed-off-by: James Smart <james.smart at broadcom.com>
---
drivers/nvme/target/fc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/nvme/target/fc.c b/drivers/nvme/target/fc.c
index e5d30bb..4a44fd3 100644
--- a/drivers/nvme/target/fc.c
+++ b/drivers/nvme/target/fc.c
@@ -2377,6 +2377,7 @@ nvmet_fc_add_port(struct nvmet_port *port)
if (!tgtport->port) {
tgtport->port = port;
port->priv = tgtport;
+ nvmet_fc_tgtport_get(tgtport);
ret = 0;
} else
ret = -EALREADY;
--
2.9.3
next prev parent reply other threads:[~2017-03-24 3:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 3:43 [PATCH 0/5] nvmet_fc: bug fixes and lldd api mods jsmart2021
2017-03-24 3:43 ` [PATCH 1/5] nvmet_fc: add target feature flags for upcall isr contexts jsmart2021
2017-04-20 10:58 ` Sagi Grimberg
2017-03-24 3:43 ` [PATCH 2/5] nvmet_fc: add req_release to lldd api jsmart2021
2017-04-20 11:02 ` Sagi Grimberg
2017-03-24 3:43 ` [PATCH 3/5] nvme_fcloop: split job struct from transport for req_release jsmart2021
2017-04-20 11:06 ` Sagi Grimberg
2017-03-24 3:43 ` [PATCH 4/5] nvmet_fc: Rework target side abort handling jsmart2021
2017-04-20 11:15 ` Sagi Grimberg
2017-03-24 3:43 ` jsmart2021 [this message]
2017-04-20 11:16 ` [PATCH 5/5] nvmet_fc: add missing reference in add_port Sagi Grimberg
2017-04-05 8:05 ` [PATCH 0/5] nvmet_fc: bug fixes and lldd api mods Sagi Grimberg
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=20170324034321.8719-6-jsmart2021@gmail.com \
--to=jsmart2021@gmail.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).