From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Arik Nemtsov <arik@wizery.com>
Cc: linux-wireless@vger.kernel.org, Jonathan Doron <jond@wizery.com>
Subject: Re: [PATCH v2 2/4] cfg80211: update missing fields in custom regulatory path
Date: Thu, 13 Nov 2014 23:55:28 +0100 [thread overview]
Message-ID: <20141113225528.GE24486@wotan.suse.de> (raw)
In-Reply-To: <1415895219-19848-2-git-send-email-arik@wizery.com>
On Thu, Nov 13, 2014 at 06:13:37PM +0200, Arik Nemtsov wrote:
> From: Jonathan Doron <jond@wizery.com>
>
> Some channels fields were not being updated in the custom regulatory
> path. Update them according to the code in handle_channel().
>
> Signed-off-by: Jonathan Doron <jonathanx.doron@intel.com>
> Signed-off-by: Arik Nemtsov <arikx.nemtsov@intel.com>
> ---
> net/wireless/reg.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/net/wireless/reg.c b/net/wireless/reg.c
> index 6459ddd..174d8f82 100644
> --- a/net/wireless/reg.c
> +++ b/net/wireless/reg.c
> @@ -1693,10 +1693,23 @@ static void handle_channel_custom(struct wiphy *wiphy,
> if (max_bandwidth_khz < MHZ_TO_KHZ(160))
> bw_flags |= IEEE80211_CHAN_NO_160MHZ;
>
> + chan->dfs_state = NL80211_DFS_USABLE;
NL80211_DFS_USABLE is 0 so this is not needed. Being explicit about it
is OK I suppose though.
> + chan->dfs_state_entered = jiffies;
OK.
> +
> + chan->beacon_found = false;
false is 0 so this is not needed but being explicit about it is OK.
> chan->flags |= map_regdom_flags(reg_rule->flags) | bw_flags;
> chan->max_antenna_gain = (int) MBI_TO_DBI(power_rule->max_antenna_gain);
> chan->max_reg_power = chan->max_power =
> (int) MBM_TO_DBM(power_rule->max_eirp);
> +
> + if (chan->flags & IEEE80211_CHAN_RADAR) {
> + if (reg_rule->dfs_cac_ms)
> + chan->dfs_cac_ms = reg_rule->dfs_cac_ms;
> + else
> + chan->dfs_cac_ms = IEEE80211_DFS_MIN_CAC_TIME_MS;
> + }
> +
> + chan->max_power = chan->max_reg_power;
> }
I rather you split this up into the stuff not required (things which
are good to be explicit about) Vs possible fixes, these last are
good fixes. Also put them as part of your first set of patches
and add my Acked-by so Johannes can already merge them. If you want
them merged faster just send them separately now.
Acked-by: Luis R. Rodriguez <mcgrof@suse.com>
Luis
next prev parent reply other threads:[~2014-11-13 22:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 16:13 [PATCH v2 1/4] cfg80211: leave invalid channels on regdomain change Arik Nemtsov
2014-11-13 16:13 ` [PATCH v2 2/4] cfg80211: update missing fields in custom regulatory path Arik Nemtsov
2014-11-13 22:55 ` Luis R. Rodriguez [this message]
2014-11-16 11:01 ` Arik Nemtsov
2014-11-13 16:13 ` [PATCH v2 3/4] cfg80211: allow wiphy specific regdomain management Arik Nemtsov
2014-11-13 23:11 ` Luis R. Rodriguez
2014-11-16 11:06 ` Arik Nemtsov
2014-11-20 20:27 ` Luis R. Rodriguez
2014-11-21 9:17 ` Arik Nemtsov
2014-11-13 16:13 ` [PATCH v2 4/4] cfg80211: Allow usermode to query wiphy specific regd info Arik Nemtsov
2014-11-13 23:13 ` Luis R. Rodriguez
2014-11-16 11:06 ` Arik Nemtsov
2014-11-20 15:22 ` Johannes Berg
2014-11-20 16:47 ` Arik Nemtsov
2014-11-20 20:54 ` Luis R. Rodriguez
2014-11-21 9:33 ` Arik Nemtsov
2014-11-21 23:38 ` Luis R. Rodriguez
2014-11-13 22:45 ` [PATCH v2 1/4] cfg80211: leave invalid channels on regdomain change Luis R. Rodriguez
2014-11-16 11:00 ` Arik Nemtsov
2014-11-20 15:17 ` Johannes Berg
2014-11-20 20:35 ` Luis R. Rodriguez
2014-11-20 20:38 ` Johannes Berg
2014-11-20 20:56 ` Luis R. Rodriguez
2014-11-20 15:17 ` Johannes Berg
2014-11-20 20:38 ` Luis R. Rodriguez
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=20141113225528.GE24486@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=arik@wizery.com \
--cc=jond@wizery.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).