Commit a5321aa5 authored by James Smart's avatar James Smart Committed by Christoph Hellwig

nvme_fc: revise comment on teardown

Per the recommendation by Sagi on:
http://lists.infradead.org/pipermail/linux-nvme/2017-April/009261.html

An extra reference was pointed out.  There's no issue with the
references, but rather a literal interpretation of what the comment
is saying.

Reword the comment to avoid confusion.
Signed-off-by: default avatarJames Smart <james.smart@broadcom.com>
Reviewed-by: default avatarJohannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: default avatarHannes Reinecke <hare@suse.com>
Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
parent 5bbecdbc
...@@ -2532,10 +2532,10 @@ nvme_fc_delete_ctrl_work(struct work_struct *work) ...@@ -2532,10 +2532,10 @@ nvme_fc_delete_ctrl_work(struct work_struct *work)
/* /*
* tear down the controller * tear down the controller
* This will result in the last reference on the nvme ctrl to * After the last reference on the nvme ctrl is removed,
* expire, calling the transport nvme_fc_nvme_ctrl_freed() callback. * the transport nvme_fc_nvme_ctrl_freed() callback will be
* From there, the transport will tear down it's logical queues and * invoked. From there, the transport will tear down it's
* association. * logical queues and association.
*/ */
nvme_uninit_ctrl(&ctrl->ctrl); nvme_uninit_ctrl(&ctrl->ctrl);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment