From: kbuild test robot <lkp@intel.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: kbuild-all@01.org, Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: [RFC PATCH] brcmfmac: brcmf_cfg80211_ops can be static
Date: Sun, 18 Mar 2018 10:31:45 +0800 [thread overview]
Message-ID: <20180318023145.GA29191@intel11> (raw)
In-Reply-To: <1521195085-439-5-git-send-email-arend.vanspriel@broadcom.com>
Fixes: 6a5eed240a1c ("brcmfmac: allocate struct brcmf_pub instance using wiphy_new()")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
cfg80211.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
index a47fe23..4133d66 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
@@ -5141,7 +5141,7 @@ static int brcmf_cfg80211_del_pmk(struct wiphy *wiphy, struct net_device *dev,
return brcmf_set_pmk(ifp, NULL, 0);
}
-struct cfg80211_ops brcmf_cfg80211_ops = {
+static struct cfg80211_ops brcmf_cfg80211_ops = {
.add_virtual_intf = brcmf_cfg80211_add_iface,
.del_virtual_intf = brcmf_cfg80211_del_iface,
.change_virtual_intf = brcmf_cfg80211_change_iface,
next prev parent reply other threads:[~2018-03-18 2:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 10:11 [PATCH 00/12] brcmfmac: data structure and firmware loading rework Arend van Spriel
2018-03-16 10:11 ` [PATCH 01/12] brcmfmac: do not convert linux error to firmware error string Arend van Spriel
2018-03-22 20:31 ` Arend van Spriel
2018-03-16 10:11 ` [PATCH 02/12] brcmfmac: use brcmf_chip_name() to store name in revinfo Arend van Spriel
2018-03-16 10:11 ` [PATCH 03/12] brcmfmac: use brcmf_chip_name() for consistency Arend van Spriel
2018-03-16 10:11 ` [PATCH 04/12] brcmfmac: allocate struct brcmf_pub instance using wiphy_new() Arend van Spriel
2018-03-18 2:31 ` kbuild test robot
2018-03-18 2:31 ` kbuild test robot [this message]
2018-03-16 10:11 ` [PATCH 05/12] brcmfmac: use wiphy debugfs dir entry Arend van Spriel
2018-03-16 10:11 ` [PATCH 06/12] brcmfmac: derive firmware filenames from basename mapping Arend van Spriel
2018-03-16 10:11 ` [PATCH 07/12] brcmfmac: pass struct in brcmf_fw_get_firmwares() Arend van Spriel
2018-03-18 2:56 ` [RFC PATCH] brcmfmac: brcmf_fw_request_is_valid() can be static kbuild test robot
2018-03-18 2:56 ` [PATCH 07/12] brcmfmac: pass struct in brcmf_fw_get_firmwares() kbuild test robot
2018-03-16 10:11 ` [PATCH 08/12] brcmfmac: introduce brcmf_fw_alloc_request() function Arend van Spriel
2018-03-16 10:11 ` [PATCH 09/12] brcmfmac: add extension to .get_fwname() callbacks Arend van Spriel
2018-03-16 10:11 ` [PATCH 10/12] brcmfmac: get rid of brcmf_fw_map_chip_to_name() Arend van Spriel
2018-03-16 10:11 ` [PATCH 11/12] brcmfmac: get rid of brcmf_fw_get_full_name() Arend van Spriel
2018-03-16 10:11 ` [PATCH 12/12] brcmfmac: add kerneldoc for struct brcmf_bus::msgbuf Arend van Spriel
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=20180318023145.GA29191@intel11 \
--to=lkp@intel.com \
--cc=arend.vanspriel@broadcom.com \
--cc=kbuild-all@01.org \
--cc=kvalo@codeaurora.org \
--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).