From: Sebastian Herbszt <herbszt@gmx.de>
To: fcoe-devel@open-fcoe.org, linux-scsi@vger.kernel.org
Cc: Vasu Dev <vasu.dev@intel.com>, Sebastian Herbszt <herbszt@gmx.de>
Subject: [PATCH] libfc: correct function name in comment
Date: Sun, 11 Oct 2015 22:35:18 +0200 [thread overview]
Message-ID: <20151011223518.00000bdb@localhost> (raw)
Use the correct function name in kernel-doc comment.
Signed-off-by: Sebastian Herbszt <herbszt@gmx.de>
Acked-by: Vasu Dev <vasu.dev@intel.com>
---
diff -U 5 -rp a/drivers/scsi/libfc/fc_npiv.c b/drivers/scsi/libfc/fc_npiv.c
--- a/drivers/scsi/libfc/fc_npiv.c 2014-09-03 19:30:11.760273300 +0200
+++ b/drivers/scsi/libfc/fc_npiv.c 2015-08-05 00:06:17.927753719 +0200
@@ -23,11 +23,11 @@
#include <scsi/libfc.h>
#include <linux/export.h>
/**
- * fc_vport_create() - Create a new NPIV vport instance
+ * libfc_vport_create() - Create a new NPIV vport instance
* @vport: fc_vport structure from scsi_transport_fc
* @privsize: driver private data size to allocate along with the Scsi_Host
*/
struct fc_lport *libfc_vport_create(struct fc_vport *vport, int privsize)
next reply other threads:[~2015-10-11 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 20:35 Sebastian Herbszt [this message]
2015-10-12 12:34 ` [PATCH] libfc: correct function name in comment Hannes Reinecke
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=20151011223518.00000bdb@localhost \
--to=herbszt@gmx.de \
--cc=fcoe-devel@open-fcoe.org \
--cc=linux-scsi@vger.kernel.org \
--cc=vasu.dev@intel.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).