From: Kalle Valo <kvalo@codeaurora.org>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: davem@davemloft.net, Larry.Finger@lwfinger.net,
chaoming_li@realsil.com.cn, jon.maloy@ericsson.com,
ying.xue@windriver.com, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [1/3] net: rtlwifi: constify rate_control_ops
Date: Thu, 24 Aug 2017 09:57:48 +0000 (UTC) [thread overview]
Message-ID: <20170824095748.41364606B7@smtp.codeaurora.org> (raw)
In-Reply-To: <1503482375-19983-2-git-send-email-arvind.yadav.cs@gmail.com>
Arvind Yadav <arvind.yadav.cs@gmail.com> wrote:
> rate_control_ops are not supposed to change at runtime. All functions
> working with rate_control_ops provided by <net/mac80211.h> work with
> const rate_control_ops. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
2 patches applied to wireless-drivers-next.git, thanks.
28b75415ad19 wireless: ipw2200: Replace PCI pool old API
9ea792a48cdd net: rsi: mac80211: constify ieee80211_ops
--
https://patchwork.kernel.org/patch/9917001/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-08-24 9:57 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 ` Kalle Valo [this message]
2017-08-23 9:59 ` [PATCH 2/3] net: rsi: mac80211: constify ieee80211_ops Arvind Yadav
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=20170824095748.41364606B7@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=arvind.yadav.cs@gmail.com \
--cc=chaoming_li@realsil.com.cn \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--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).