From: Johannes Berg <johannes@sipsolutions.net>
To: Arik Nemtsov <arik@wizery.com>
Cc: linux-wireless@vger.kernel.org, "Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [PATCH 2/2] cfg80211: avoid reg-hints in self-managed only systems
Date: Tue, 06 Jan 2015 14:59:04 +0100 [thread overview]
Message-ID: <1420552744.1966.31.camel@sipsolutions.net> (raw)
In-Reply-To: <1420541766.1966.18.camel@sipsolutions.net> (sfid-20150106_115615_591316_7E790C4F)
On Tue, 2015-01-06 at 11:56 +0100, Johannes Berg wrote:
> On Thu, 2015-01-01 at 13:42 +0200, Arik Nemtsov wrote:
> > When a system contains only self-managed regulatory devices all hints
> > from the regulatory core are ignored. Stop hint processing early in this
> > case. These systems usually don't have CRDA deployed, which results in
> > endless (irrelevent) logs of the form:
> > cfg80211: Calling CRDA to update world regulatory domain
>
> Applied.
I take that back - dropped again. This was causing spurious messages in
the hwsim test run VM, saying something like "couldn't set reg domain:
-7". Maybe at that point not a single wiphy existed?
johannes
next prev parent reply other threads:[~2015-01-06 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 11:42 [PATCH 1/2] cfg80211: introduce sync regdom set API for self-managed Arik Nemtsov
2015-01-01 11:42 ` [PATCH 2/2] cfg80211: avoid reg-hints in self-managed only systems Arik Nemtsov
2015-01-06 10:56 ` Johannes Berg
2015-01-06 13:59 ` Johannes Berg [this message]
2015-01-06 14:04 ` Arik Nemtsov
2015-01-07 13:38 ` Arik Nemtsov
2015-01-07 13:42 ` Johannes Berg
2015-01-07 13:45 ` Arik Nemtsov
2015-01-06 10:54 ` [PATCH 1/2] cfg80211: introduce sync regdom set API for self-managed Johannes Berg
2015-01-07 13:35 ` Arik Nemtsov
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=1420552744.1966.31.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arik@wizery.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@suse.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).