Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759969AbbKTLzn (ORCPT ); Fri, 20 Nov 2015 06:55:43 -0500 Received: from s3.sipsolutions.net ([5.9.151.49]:51884 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759595AbbKTLzl (ORCPT ); Fri, 20 Nov 2015 06:55:41 -0500 Message-ID: <1448020533.3141.27.camel@sipsolutions.net> Subject: Re: [PATCH] wireless: change cfg80211 regulatory domain info as debug messages From: Johannes Berg To: Stefan Lippers-Hollmann , Dave Young Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, davem@davemloft.net Date: Fri, 20 Nov 2015 12:55:33 +0100 In-Reply-To: <20151115192547.3fd1b3cc@mir> References: <20151115073105.GA18846@dhcp-128-65.nay.redhat.com> <20151115192547.3fd1b3cc@mir> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.1-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1559 Lines: 36 On Sun, 2015-11-15 at 19:25 +0100, 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. > Hm. I kinda sympathize with both points of view here, not sure what to do. Maybe we could skip this for the world regdomain only? It doesn't really change, and we typically don't care that much for it? That'd probably get rid of most of the lines already. Alternatively, perhaps the internal computations should be more transparently visible through some other mechanism? johannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/