From: Chaitanya Kulkarni <kch@nvidia.com>
To: <james.smart@broadcom.com>
Cc: <linux-nvme@lists.infradead.org>, <hch@lst.de>,
<sagi@grimberg.me>, Chaitanya Kulkarni <kch@nvidia.com>
Subject: [PATCH] nvmet-fc: remove repeated word from comment
Date: Tue, 16 Jan 2024 20:43:34 -0800 [thread overview]
Message-ID: <20240117044334.17224-1-kch@nvidia.com> (raw)
Remove the repeated word "port" from the comment. Also, since there is
an ample space to accommodate more words per line by maintaining
80-char limit use this opportunity to adjust the overall comment.
Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
---
drivers/nvme/target/fc.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/nvme/target/fc.c b/drivers/nvme/target/fc.c
index bda7a3009e85..757a7348a8b0 100644
--- a/drivers/nvme/target/fc.c
+++ b/drivers/nvme/target/fc.c
@@ -1315,12 +1315,11 @@ nvmet_fc_portentry_unbind_tgt(struct nvmet_fc_tgtport *tgtport)
}
/*
- * called when a new targetport is registered. Looks in the
- * existing nvmet port_entries to see if the nvmet layer is
- * configured for the targetport's wwn's. (the targetport existed,
- * nvmet configured, the lldd unregistered the tgtport, and is now
- * reregistering the same targetport). If so, set the nvmet port
- * port entry on the targetport.
+ * called when a new targetport is registered. Looks in the existing nvmet
+ * port_entries to see if the nvmet layer is configured for the targetport's
+ * wwn's. (the targetport existed, nvmet configured, the lldd unregistered the
+ * tgtport, and is now reregistering the same targetport). If so, set the
+ * nvmet port entry on the targetport.
*/
static void
nvmet_fc_portentry_rebind_tgt(struct nvmet_fc_tgtport *tgtport)
--
2.40.0
next reply other threads:[~2024-01-17 4:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 4:43 Chaitanya Kulkarni [this message]
2024-01-17 14:05 ` [PATCH] nvmet-fc: remove repeated word from comment 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=20240117044334.17224-1-kch@nvidia.com \
--to=kch@nvidia.com \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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