From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Can we make ieee80211_iface_combination.limits non-const?
Date: Thu, 26 Jun 2014 22:06:27 +0200 [thread overview]
Message-ID: <1403813187.4463.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <53AC6454.5090605@candelatech.com> (sfid-20140626_202012_477893_089B637F)
On Thu, 2014-06-26 at 11:20 -0700, Ben Greear wrote:
> Depending on firmware loaded (and/or module options), a different
> number of vdev interfaces may be supported.
>
> Can we remove the const from the "struct ieee80211_iface_limit *limits"
> member of ieee80211_iface_combination?
No, it would break drivers who actually have a static const for the
pointer target.
You don't have to assign something that's const, but you also can't be
changing it on the fly after wiphy registration anyway.
johannes
next prev parent reply other threads:[~2014-06-26 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 18:20 Can we make ieee80211_iface_combination.limits non-const? Ben Greear
2014-06-26 20:06 ` Johannes Berg [this message]
2014-06-26 20:23 ` Ben Greear
2014-06-27 7:44 ` Johannes Berg
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=1403813187.4463.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.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).