From: Johannes Berg <johannes@sipsolutions.net>
To: Seth Forshee <seth.forshee@canonical.com>,
Matthias May <matthias.may@neratec.com>
Cc: cory novak <cory.novak@gmail.com>, wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] [RFC] wireless-regdb: Update 5 GHz rules for Canada
Date: Wed, 01 Mar 2017 16:35:17 +0100 [thread overview]
Message-ID: <1488382517.2698.3.camel@sipsolutions.net> (raw)
In-Reply-To: <20170301150757.GL122517@ubuntu-hedt>
> >
> > > static inline int
> > > ieee80211_chandef_max_power(struct cfg80211_chan_def *chandef)
> > > {
> > > switch (chandef->width) {
> > > case NL80211_CHAN_WIDTH_5:
> > > return min(chandef->chan->max_reg_power - 6,
> > > chandef->chan->max_power);
> > > case NL80211_CHAN_WIDTH_10:
> > > return min(chandef->chan->max_reg_power - 3,
> > > chandef->chan->max_power);
> > > default:
> > > break;
> > > }
> > > return chandef->chan->max_power;
> > > }
> >
> > This looks to me like it already handles the reduction of power
> > according to bandwidth.
>
> Johannes, just wanted to confirm that based on this you no longer
> have any objection to the changes.
Yep, looks fine.
johannes
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2017-03-01 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPw1JcdLDkW9xEUfh-764kuC643DAJ+qWNf4RxmoyUXbpc-D5w@mail.gmail.com>
2017-02-06 19:12 ` [wireless-regdb] Fwd: possible mismatch Canadian regulatory info cory novak
2017-02-06 19:39 ` Seth Forshee
2017-02-06 19:44 ` cory novak
2017-02-06 20:50 ` [wireless-regdb] [RFC] wireless-regdb: Update 5 GHz rules for Canada Seth Forshee
2017-02-07 7:52 ` Johannes Berg
2017-02-07 14:04 ` Seth Forshee
2017-02-07 14:15 ` Johannes Berg
2017-02-13 13:58 ` Matthias May
2017-03-01 15:07 ` Seth Forshee
2017-03-01 15:35 ` Johannes Berg [this message]
2017-03-01 15:49 ` Seth Forshee
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=1488382517.2698.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=cory.novak@gmail.com \
--cc=matthias.may@neratec.com \
--cc=seth.forshee@canonical.com \
--cc=wireless-regdb@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.