From: Dave Young <dyoung@redhat.com>
To: Stefan Lippers-Hollmann <s.l-h@gmx.de>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, davem@davemloft.net,
johannes@sipsolutions.net
Subject: Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages
Date: Mon, 16 Nov 2015 09:58:45 +0800 [thread overview]
Message-ID: <20151116015845.GA3439@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <20151115192547.3fd1b3cc@mir>
Hi,
On 11/15/15 at 07:25pm, Stefan Lippers-Hollmann wrote:
> Hi
>
> On 2015-11-15, Dave Young wrote:
> > cfg80211 module prints a lot of messages like below. Actually printing
> > once is acceptable but sometimes it will print again and again, it looks
> > very annoying. It is better to change these detail messages to debugging
> > only.
>
> It is a lot of info, easily repeated 3 times on boot, but it's also the
> only real chance to determine why you ended up with the regulatory
> domain settings you got, rather than just the values itself. Given that
> a lot (most?) of officially shipping wireless devices are misconfigured
> (wrong EEPROM regdom settings for the region they're sold in) and
> considering that the limits can even change at runtime (IEEE 802.11d),
> it is imho quite important not just to be able what the current
> restrictions (iw reg get) are, but also why the kernel settled on those.
If it is really important then a kernel cmdline param to disable the logs
sounds better?
Thanks
Dave
next prev parent reply other threads:[~2015-11-16 1:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 7:31 Dave Young
2015-11-15 17:38 ` Joe Perches
2015-11-16 1:59 ` Dave Young
2015-11-16 10:38 ` Johannes Berg
2015-11-15 18:25 ` Stefan Lippers-Hollmann
2015-11-16 1:58 ` Dave Young [this message]
2015-11-20 11:55 ` Johannes Berg
2015-11-23 1:37 ` Dave Young
2015-12-11 14:26 ` Johannes Berg
2015-12-17 3:19 ` Dave Young
2015-12-17 7:58 ` Johannes Berg
2015-12-11 14:38 ` Johannes Berg
2015-12-17 3:16 ` Dave Young
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=20151116015845.GA3439@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.l-h@gmx.de \
/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
all inboxes | Powered by JetHome®