From: Johannes Berg <johannes@sipsolutions.net>
To: Matthias May <matthias.may@neratec.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCHv2 1/4] cfg80211: handle minimum bandwidth for quarter and half rates
Date: Thu, 11 Jun 2015 13:44:19 +0200 [thread overview]
Message-ID: <1434023059.1915.12.camel@sipsolutions.net> (raw)
In-Reply-To: <1434020791-16291-2-git-send-email-matthias.may@neratec.com> (sfid-20150611_130650_868019_E29B6AA4)
On Thu, 2015-06-11 at 13:06 +0200, Matthias May wrote:
> const struct ieee80211_reg_rule *freq_reg_info(struct wiphy *wiphy,
> - u32 center_freq)
> + u32 center_freq, u32 min_bw)
> {
> const struct ieee80211_regdomain *regd;
> + const struct ieee80211_reg_rule *rr_tmp = NULL;
> + const struct ieee80211_reg_rule *reg_rule = NULL;
> + u32 bw;
>
> regd = reg_get_regdomain(wiphy);
>
> - return freq_reg_info_regd(wiphy, center_freq, regd);
> + for(bw=min_bw; bw <= MHZ_TO_KHZ(20); bw=bw*2) {
> + rr_tmp = freq_reg_info_regd(wiphy, center_freq, bw, regd);
> + if(!reg_rule || !IS_ERR(rr_tmp))
> + reg_rule = rr_tmp;
> + }
> +
> + return reg_rule;
This makes no sense to me.
You have the same code below, but why would you care? You can just look
at the reg_rule's max_bandwidth, no?
johannes
next prev parent reply other threads:[~2015-06-11 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 11:06 [PATCHv2 0/4] Handle minimum bandwidth for quarter and half rates Matthias May
2015-06-11 11:06 ` [PATCHv2 1/4] cfg80211: handle " Matthias May
2015-06-11 11:33 ` Johannes Berg
2015-06-11 11:44 ` Johannes Berg [this message]
2015-06-11 12:46 ` Matthias May
2015-06-11 15:22 ` Johannes Berg
2015-06-11 11:06 ` [PATCHv2 2/4] ath: send minimum bandwidth to handle Matthias May
2015-06-11 11:06 ` [PATCHv2 3/4] brcm80211: " Matthias May
2015-06-11 11:06 ` [PATCHv2 4/4] rtlwifi: " Matthias May
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=1434023059.1915.12.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.may@neratec.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.