From: Arik Nemtsov <arik@wizery.com>
To: <linux-wireless@vger.kernel.org>
Cc: Luciano Coelho <coelho@ti.com>, Arik Nemtsov <arik@wizery.com>
Subject: [PATCH 01/10] wlcore: fix sparse warnings related to static functions
Date: Tue, 15 May 2012 17:08:51 +0300 [thread overview]
Message-ID: <1337090940-13750-1-git-send-email-arik@wizery.com> (raw)
The "static" modifier was mistakenly forgotten for some functions.
Signed-off-by: Arik Nemtsov <arik@wizery.com>
---
These patches apply on top of the wl18xx support series.
drivers/net/wireless/ti/wl18xx/main.c | 2 +-
drivers/net/wireless/ti/wlcore/main.c | 7 ++++---
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/net/wireless/ti/wl18xx/main.c b/drivers/net/wireless/ti/wl18xx/main.c
index f1fef39..d7e48db 100644
--- a/drivers/net/wireless/ti/wl18xx/main.c
+++ b/drivers/net/wireless/ti/wl18xx/main.c
@@ -1097,7 +1097,7 @@ static struct ieee80211_sta_ht_cap wl18xx_mimo_ht_cap = {
},
};
-int __devinit wl18xx_probe(struct platform_device *pdev)
+static int __devinit wl18xx_probe(struct platform_device *pdev)
{
struct wl1271 *wl;
struct ieee80211_hw *hw;
diff --git a/drivers/net/wireless/ti/wlcore/main.c b/drivers/net/wireless/ti/wlcore/main.c
index f4b036e..659634b 100644
--- a/drivers/net/wireless/ti/wlcore/main.c
+++ b/drivers/net/wireless/ti/wlcore/main.c
@@ -1212,7 +1212,8 @@ static struct sk_buff *wl12xx_alloc_dummy_packet(struct wl1271 *wl)
#ifdef CONFIG_PM
-int wl1271_validate_wowlan_pattern(struct cfg80211_wowlan_trig_pkt_pattern *p)
+static int wl1271_validate_wowlan_pattern(
+ struct cfg80211_wowlan_trig_pkt_pattern *p)
{
int num_fields = 0, in_field = 0, fields_size = 0;
int i, pattern_len = 0;
@@ -1355,7 +1356,7 @@ void wl1271_rx_filter_flatten_fields(struct wl12xx_rx_filter *filter,
* Allocates an RX filter returned through f
* which needs to be freed using rx_filter_free()
*/
-int wl1271_convert_wowlan_pattern_to_rx_filter(
+static int wl1271_convert_wowlan_pattern_to_rx_filter(
struct cfg80211_wowlan_trig_pkt_pattern *p,
struct wl12xx_rx_filter **f)
{
@@ -4820,7 +4821,7 @@ static struct bin_attribute fwlog_attr = {
.read = wl1271_sysfs_read_fwlog,
};
-void wl1271_connection_loss_work(struct work_struct *work)
+static void wl1271_connection_loss_work(struct work_struct *work)
{
struct delayed_work *dwork;
struct wl1271 *wl;
--
1.7.9.5
next reply other threads:[~2012-05-15 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 14:08 Arik Nemtsov [this message]
2012-05-15 14:08 ` [PATCH 02/10] wlcore: use the original elp time in forced_ps mode Arik Nemtsov
2012-05-15 14:08 ` [PATCH 03/10] wlcore: fix dynamic_ps_timeout time regression Arik Nemtsov
2012-05-15 14:08 ` [PATCH 04/10] wlcore: fixes for connection_loss_work Arik Nemtsov
2012-05-15 14:08 ` [PATCH 05/10] wlcore: use correct link for bcast/multicast frames Arik Nemtsov
2012-05-15 14:08 ` [PATCH 06/10] wlcore: flush before stopping AP Arik Nemtsov
2012-05-15 14:08 ` [PATCH 07/10] wlcore: modify bss loss parameters Arik Nemtsov
2012-05-15 14:08 ` [PATCH 08/10] wlcore: increase number of BA sessions to 3 Arik Nemtsov
2012-05-15 14:08 ` [PATCH 09/10] wl18xx: add dependency on mac80211 Arik Nemtsov
2012-05-15 14:09 ` [PATCH 10/10] wlcore: set wl->ht_cap per-band Arik Nemtsov
2012-06-05 14:30 ` [PATCH 01/10] wlcore: fix sparse warnings related to static functions Luciano Coelho
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=1337090940-13750-1-git-send-email-arik@wizery.com \
--to=arik@wizery.com \
--cc=coelho@ti.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).