From: "Peter Große" <pegro@friiks.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Peter Große" <pegro@friiks.de>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Fix setting TX power on monitor interfaces
Date: Tue, 19 Dec 2017 20:25:26 +0100 [thread overview]
Message-ID: <20171219202526.5bd4568c@fem-net.de> (raw)
In-Reply-To: <1513677210.26145.10.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
On Tue, 19 Dec 2017 10:53:30 +0100
Johannes Berg <johannes@sipsolutions.net> wrote:
> > + if (has_monitor) {
> > + sdata = rtnl_dereference(local->monitor_sdata);
> > + if (sdata) {
> > + sdata->user_power_level = local->user_power_level;
> > + if (txp_type != sdata->vif.bss_conf.txpower_type)
> > + update_txp_type = true;
> > + sdata->vif.bss_conf.txpower_type = txp_type;
> > +
> > + ieee80211_recalc_txpower(sdata, update_txp_type);
> > + }
> > + }
>
> But do we really need this? I think we can probably live with just not
> having monitor handled here, i.e. only have the "if monitor continue;"
> part?
I don't mind. I just thought, if I call ieee80211_recalc_txpower on the
monitor_sdata interface when called explicitly, I would also do it when
iterating over all interfaces, just to be consistent. I don't know, whether
there are drivers out there, that store power limits on monitor interfaces
separately for injection or whatever.
I can send a patch without the quoted part.
Regards
Peter
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-12-19 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 16:34 Setting TX power on a monitoring interface Peter Große
2017-11-27 11:43 ` Johannes Berg
2017-11-27 15:07 ` Peter Große
2017-12-01 14:49 ` Johannes Berg
2017-12-01 17:34 ` Peter Große
2017-12-09 19:53 ` Johannes Berg
2017-12-13 17:29 ` [PATCH] mac80211: Fix setting TX power on monitor interfaces Peter Große
2017-12-19 9:53 ` Johannes Berg
2017-12-19 19:25 ` Peter Große [this message]
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=20171219202526.5bd4568c@fem-net.de \
--to=pegro@friiks.de \
--cc=johannes@sipsolutions.net \
--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).