From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: linux-wireless@vger.kernel.org, mcgrof@do-not-panic.com
Subject: Re: [RFC 1/5] cfg80211: regulatory rules, fix bw checking
Date: Wed, 15 Jan 2014 14:23:48 +0100 [thread overview]
Message-ID: <1389792228.4338.7.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1389720570-2430-2-git-send-email-janusz.dziedzic@tieto.com> (sfid-20140114_182945_998805_0069F355)
On Tue, 2014-01-14 at 18:29 +0100, Janusz Dziedzic wrote:
> Allow BW cross over REG_RULES if rules continous.
>
> Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>
> ---
> I am not sure about rule_intersect() here ...
I'm not sure about the whole thing ...
We did discuss something like this previously (and see our todo list on
the wiki), but this isn't just some arbitrary internal change, it
completely changes the interpretation of the regulatory database.
At a minimum, that means you need a big commit log discussing the impact
of the changes etc.
johannes
next prev parent reply other threads:[~2014-01-15 13:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 17:29 [RFC 0/5] Implement DFS CAC time as regulatory param Janusz Dziedzic
2014-01-14 17:29 ` [RFC 1/5] cfg80211: regulatory rules, fix bw checking Janusz Dziedzic
2014-01-15 13:23 ` Johannes Berg [this message]
2014-01-15 16:05 ` Janusz Dziedzic
2014-01-15 20:17 ` Johannes Berg
2014-01-14 17:29 ` [RFC 2/5] cfg80211: regulatory, introduce DFS CAC time Janusz Dziedzic
2014-01-15 13:24 ` Johannes Berg
2014-01-14 17:29 ` [RFC 3/5] cfg80211: parse DFS CAC time for internal regdb option Janusz Dziedzic
2014-01-14 17:29 ` [RFC 4/5] nl80211: add DFS CAC time option Janusz Dziedzic
2014-01-15 13:25 ` Johannes Berg
2014-01-14 17:29 ` [RFC 5/5] cfg80211: setup CAC time in db.txt for PL Janusz Dziedzic
2014-01-15 13:25 ` Johannes Berg
2014-01-24 23:31 ` [RFC 0/5] Implement DFS CAC time as regulatory param 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=1389792228.4338.7.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=janusz.dziedzic@tieto.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 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).