From: Adrian Bunk <bunk@stusta.de>
To: James.Bottomley@SteelEye.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [2.6 patch] SCSI NCR_Q720.c: make some code static
Date: Mon, 15 Nov 2004 03:21:05 +0100 [thread overview]
Message-ID: <20041115022105.GU2249@stusta.de> (raw)
The patch below makes two needlessly global structs static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.10-rc1-mm5-full/drivers/scsi/NCR_Q720.c.old 2004-11-13 16:34:15.000000000 +0100
+++ linux-2.6.10-rc1-mm5-full/drivers/scsi/NCR_Q720.c 2004-11-13 16:34:32.000000000 +0100
@@ -48,7 +48,7 @@
struct Scsi_Host *hosts[4];
};
-struct scsi_host_template NCR_Q720_tpnt = {
+static struct scsi_host_template NCR_Q720_tpnt = {
.module = THIS_MODULE,
.proc_name = "NCR_Q720",
};
@@ -345,7 +345,7 @@
static short NCR_Q720_id_table[] = { NCR_Q720_MCA_ID, 0 };
-struct mca_driver NCR_Q720_driver = {
+static struct mca_driver NCR_Q720_driver = {
.id_table = NCR_Q720_id_table,
.driver = {
.name = "NCR_Q720",
next reply other threads:[~2004-11-15 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 2:21 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-23 10:15 [2.6 patch] SCSI NCR_Q720.c: make some code static Adrian Bunk
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=20041115022105.GU2249@stusta.de \
--to=bunk@stusta.de \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox