From: Adrian Bunk <bunk@stusta.de>
To: support@lsil.com
Cc: mpt_linux_developer@lsil.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [2.6 patch] drivers/message/fusion/mptfc.c: make 2 functions static
Date: Thu, 19 Jan 2006 02:02:33 +0100 [thread overview]
Message-ID: <20060119010233.GT19398@stusta.de> (raw)
This patch makes two needlessly global functions static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
drivers/message/fusion/mptfc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- linux-2.6.16-rc1-mm1-full/drivers/message/fusion/mptfc.c.old 2006-01-18 23:16:09.000000000 +0100
+++ linux-2.6.16-rc1-mm1-full/drivers/message/fusion/mptfc.c 2006-01-18 23:16:34.000000000 +0100
@@ -93,7 +93,7 @@
static int mptfcTaskCtx = -1;
static int mptfcInternalCtx = -1; /* Used only for internal commands */
-int mptfc_slave_alloc(struct scsi_device *device);
+static int mptfc_slave_alloc(struct scsi_device *device);
static int mptfc_qcmd(struct scsi_cmnd *SCpnt,
void (*done)(struct scsi_cmnd *));
@@ -153,7 +153,7 @@
static struct scsi_transport_template *mptfc_transport_template = NULL;
-struct fc_function_template mptfc_transport_functions = {
+static struct fc_function_template mptfc_transport_functions = {
.dd_fcrport_size = 8,
.show_host_node_name = 1,
.show_host_port_name = 1,
@@ -432,7 +432,7 @@
* Return non-zero if allocation fails.
* Init memory once per LUN.
*/
-int
+static int
mptfc_slave_alloc(struct scsi_device *sdev)
{
MPT_SCSI_HOST *hd;
next reply other threads:[~2006-01-19 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 1:02 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-25 1:00 [2.6 patch] drivers/message/fusion/mptfc.c: make 2 functions static Adrian Bunk
2006-01-25 16:26 Moore, Eric
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=20060119010233.GT19398@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mpt_linux_developer@lsil.com \
--cc=support@lsil.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).