From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: davem@davemloft.net, Larry.Finger@lwfinger.net,
chaoming_li@realsil.com.cn, kvalo@codeaurora.org,
jon.maloy@ericsson.com, ying.xue@windriver.com
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: [PATCH 2/3] net: rsi: mac80211: constify ieee80211_ops
Date: Wed, 23 Aug 2017 15:29:34 +0530 [thread overview]
Message-ID: <1503482375-19983-3-git-send-email-arvind.yadav.cs@gmail.com> (raw)
In-Reply-To: <1503482375-19983-1-git-send-email-arvind.yadav.cs@gmail.com>
ieee80211_ops are not supposed to change at runtime. All functions
working with ieee80211_ops provided by <net/mac80211.h> work with
const ieee80211_ops. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
---
drivers/net/wireless/rsi/rsi_91x_mac80211.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/rsi/rsi_91x_mac80211.c b/drivers/net/wireless/rsi/rsi_91x_mac80211.c
index 021e5ac..67532fb 100644
--- a/drivers/net/wireless/rsi/rsi_91x_mac80211.c
+++ b/drivers/net/wireless/rsi/rsi_91x_mac80211.c
@@ -1177,7 +1177,7 @@ static void rsi_reg_notify(struct wiphy *wiphy,
adapter->dfs_region = request->dfs_region;
}
-static struct ieee80211_ops mac80211_ops = {
+static const struct ieee80211_ops mac80211_ops = {
.tx = rsi_mac80211_tx,
.start = rsi_mac80211_start,
.stop = rsi_mac80211_stop,
--
1.9.1
next prev parent reply other threads:[~2017-08-23 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 9:59 [PATCH 0/3] constify *_ops Arvind Yadav
[not found] ` <1503482375-19983-1-git-send-email-arvind.yadav.cs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-23 9:59 ` [PATCH 1/3] net: rtlwifi: constify rate_control_ops Arvind Yadav
2017-08-24 9:57 ` [1/3] " Kalle Valo
2017-08-23 9:59 ` Arvind Yadav [this message]
2017-08-23 9:59 ` [PATCH 3/3] net: rsi: netlink: constify genl_ops Arvind Yadav
2017-08-23 10:02 ` Kalle Valo
2017-08-23 10:05 ` Arvind Yadav
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=1503482375-19983-3-git-send-email-arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ying.xue@windriver.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).