From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v4] cfg80211: regulatory introduce maximum bandwidth calculation
Date: Thu, 20 Feb 2014 08:08:10 +0100 [thread overview]
Message-ID: <1392880090.5073.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CALhHN=qnWsY3cEewxAOR+KafW8L-VFFG9djk5shS_BSdepKqnw@mail.gmail.com> (sfid-20140220_070758_613044_2C66DDE2)
On Thu, 2014-02-20 at 07:07 +0100, Janusz Dziedzic wrote:
> > What happens if an old kernel gets a new wireless-regdb with AUTO on
> > all of its 5 GHz regdomain for the country it using ? I see no mention
> > of this anywhere in the documentation and at least from the code
> > review I just did it seemed like we'd use 0. I hope I'm wrong as
> > otherwise that'd introduce a severe regression when this is introduced
> > to wireless-regdb.
> Old-kernel + new wireless-regdb + new crda.
> In case of AUTO we will not set NL80211_ATTR_FREQ_RANGE_MAX_BW we will
> get -EINVAL
That seems like a problem.
johannes
next prev parent reply other threads:[~2014-02-20 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 8:52 [PATCH v4] cfg80211: regulatory introduce maximum bandwidth calculation Janusz Dziedzic
2014-01-31 14:07 ` Johannes Berg
2014-01-31 16:18 ` Janusz Dziedzic
2014-01-31 20:04 ` Johannes Berg
2014-02-19 18:51 ` Luis R. Rodriguez
2014-02-20 6:07 ` Janusz Dziedzic
2014-02-20 7:08 ` Johannes Berg [this message]
2014-02-20 7:25 ` Janusz Dziedzic
2014-02-21 23:08 ` 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=1392880090.5073.2.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).