From: Sami Laine <laine.j.sami@gmail.com>
To: daeseok.youn@gmail.com
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: [PATCH next-20140424] staging/cxt1e1: sparse warning corrections
Date: Sat, 26 Apr 2014 18:53:15 +0300 [thread overview]
Message-ID: <20140426155315.GA4745@acer> (raw)
From: Sami Laine <laine.j.sami@gmail.com>
Corrected sparse static declaration warnings.
Signed-off-by: Sami Laine <laine.j.sami@gmail.com>
---
diff --git a/drivers/staging/cxt1e1/hwprobe.c b/drivers/staging/cxt1e1/hwprobe.c
index cc2151e..2899258 100644
--- a/drivers/staging/cxt1e1/hwprobe.c
+++ b/drivers/staging/cxt1e1/hwprobe.c
@@ -40,10 +40,10 @@ struct net_device * __init c4_add_dev(hdw_info_t *, int, unsigned long,
unsigned long, int, int);
-struct s_hdw_info hdw_info[MAX_BOARDS];
+static struct s_hdw_info hdw_info[MAX_BOARDS];
-void __init
+static void __init
show_two(hdw_info_t *hi, int brdno)
{
ci_t *ci;
@@ -88,7 +88,7 @@ show_two(hdw_info_t *hi, int brdno)
}
-void __init
+static void __init
hdw_sn_get(hdw_info_t *hi, int brdno)
{
/* obtain hardware EEPROM information */
@@ -145,7 +145,7 @@ hdw_sn_get(hdw_info_t *hi, int brdno)
}
- void __init
+static void __init
prep_hdw_info(void)
{
hdw_info_t *hi;
@@ -164,7 +164,7 @@ prep_hdw_info(void)
}
}
-void
+static void
cleanup_ioremap(void)
{
hdw_info_t *hi;
@@ -187,7 +187,7 @@ cleanup_ioremap(void)
}
-void
+static void
cleanup_devs(void)
{
hdw_info_t *hi;
@@ -287,7 +287,7 @@ c4_hdw_init(struct pci_dev *pdev, int found)
return 1;
}
-status_t __init
+static status_t __init
c4hw_attach_all(void)
{
hdw_info_t *hi;
next reply other threads:[~2014-04-26 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 15:53 Sami Laine [this message]
2014-04-28 0:05 ` [PATCH next-20140424] staging/cxt1e1: sparse warning corrections DaeSeok Youn
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=20140426155315.GA4745@acer \
--to=laine.j.sami@gmail.com \
--cc=daeseok.youn@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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