From: Vasu Dev <vasu.dev@intel.com>
To: linux-scsi@vger.kernel.org
Cc: fcoe-devel@open-fcoe.org,
target-devel <target-devel@vger.kernel.org>,
Bart Van Assche <bart.vanassche@sandisk.com>,
Vasu Dev <vasu.dev@intel.com>
Subject: [PATCH 1/3] libfc: Fix a typo in a source code comment
Date: Fri, 05 Jun 2015 14:20:40 -0700 [thread overview]
Message-ID: <20150605212040.6054.1198.stgit@lin-nd1-054.jf.intel.com> (raw)
In-Reply-To: <20150605212003.6054.15351.stgit@lin-nd1-054.jf.intel.com>
From: Bart Van Assche <bart.vanassche@sandisk.com>
Signed-off-by: Bart Van Assche <bart.vanassche@sandisk.com>
Signed-off-by: Vasu Dev <vasu.dev@intel.com>
---
drivers/scsi/libfc/fc_fcp.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/libfc/fc_fcp.c b/drivers/scsi/libfc/fc_fcp.c
index c679594..4cd49d4 100644
--- a/drivers/scsi/libfc/fc_fcp.c
+++ b/drivers/scsi/libfc/fc_fcp.c
@@ -191,7 +191,7 @@ static void fc_fcp_pkt_hold(struct fc_fcp_pkt *fsp)
}
/**
- * fc_fcp_pkt_destory() - Release hold on a fcp_pkt
+ * fc_fcp_pkt_destroy() - Release hold on a fcp_pkt
* @seq: The sequence that the FCP packet is on (required by destructor API)
* @fsp: The FCP packet to be released
*
next prev parent reply other threads:[~2015-06-05 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 21:20 [PATCH 0/3] libfc patches for kernel v4.2 Vasu Dev
2015-06-05 21:20 ` Vasu Dev [this message]
2015-06-05 21:20 ` [PATCH 2/3] libfc: Fix fc_exch_recv_req() error path Vasu Dev
2015-06-05 21:20 ` Vasu Dev
2015-06-05 21:20 ` [PATCH 3/3] libfc: Fix fc_fcp_cleanup_each_cmd() Vasu Dev
[not found] ` <20150605212003.6054.15351.stgit-CpQRhGjq1eVJhAXLHP3yBbvm/XP+8Wra@public.gmane.org>
2015-06-05 21:28 ` [PATCH 0/3] libfc patches for kernel v4.2 Vasu Dev
2015-06-29 20:29 ` Vasu Dev
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=20150605212040.6054.1198.stgit@lin-nd1-054.jf.intel.com \
--to=vasu.dev@intel.com \
--cc=bart.vanassche@sandisk.com \
--cc=fcoe-devel@open-fcoe.org \
--cc=linux-scsi@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.