Return-path: Received: from mo4-p05-ob.smtp.rzone.de ([81.169.146.180]:63471 "EHLO mo4-p05-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751574AbbKOScN (ORCPT ); Sun, 15 Nov 2015 13:32:13 -0500 Date: Sun, 15 Nov 2015 19:25:47 +0100 From: Stefan Lippers-Hollmann To: Dave Young 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 Message-ID: <20151115192547.3fd1b3cc@mir> (sfid-20151115_193253_087259_9D73474E) In-Reply-To: <20151115073105.GA18846@dhcp-128-65.nay.redhat.com> References: <20151115073105.GA18846@dhcp-128-65.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: 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. Regards Stefan Lippers-Hollmann