From: "Arend van Spriel" <arend@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: linux-wireless@vger.kernel.org, dquan@qca.qualcomm.com
Subject: Re: [RFT 2/2] cfg80211: add 5 GHz UNII band regulatory hints
Date: Mon, 13 Aug 2012 15:58:36 +0200 [thread overview]
Message-ID: <5029080C.3060503@broadcom.com> (raw)
In-Reply-To: <1344644750-14000-3-git-send-email-mcgrof@do-not-panic.com>
On 08/11/2012 02:25 AM, Luis R. Rodriguez wrote:
> +static void reg_unii_5ghz_beacon_hint_unii(struct wiphy *wiphy,
> + struct ieee80211_channel *chan,
> + enum reg_5ghz_unii_band unii_band)
> +{
> + struct ieee80211_supported_band *sband;
> + unsigned int i;
> +
> + assert_cfg80211_lock();
> +
> + sband = wiphy->bands[chan->band];
> +
> + /*
> + * Only process UNII 1 hints for UNII 1 channels
> + * Only process UNII 3 hints for UNII 3 channels
> + */
> + for (i = 0; i < sband->n_channels; i++) {
> + struct ieee80211_channel *c = &sband->channels[i];
> +
> + switch (unii_band) {
> + case REG_5GHZ_UNII_1:
> + if (!reg_is_5ghz_unii_1(c))
> + continue;
> + break;
> + case REG_5GHZ_UNII_3:
> + if (!reg_is_5ghz_unii_3(c))
> + continue;
> + break;
> + default:
> + WARN_ONCE(1, "unexpected regulatory unii hint\n");
> + continue;
> + }
> +
> + reg_chan_process_beacon_hint(wiphy, chan);
Not sure, but reading the description I think variable 'c' should be
passed here instead of 'chan'.
> + }
Gr. AvS
prev parent reply other threads:[~2012-08-13 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 0:25 [RFT 0/2] cfg80211: UNII regulatory hints Luis R. Rodriguez
2012-08-11 0:25 ` [RFT 1/2] cfg80211: add a helper for processing 5 GHz beacon hints Luis R. Rodriguez
2012-08-11 0:25 ` [RFT 2/2] cfg80211: add 5 GHz UNII band regulatory hints Luis R. Rodriguez
2012-08-13 13:58 ` Arend van Spriel [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=5029080C.3060503@broadcom.com \
--to=arend@broadcom.com \
--cc=dquan@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.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 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.