From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from opensource2.wolfsonmicro.com (opensource.wolfsonmicro.com [80.75.67.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 56758B70E2 for ; Tue, 8 Feb 2011 02:50:00 +1100 (EST) Date: Mon, 7 Feb 2011 15:49:53 +0000 From: Mark Brown To: Alan Stern Subject: Re: [PATCH] PM: Hide CONFIG_PM from users Message-ID: <20110207154953.GN10564@opensource.wolfsonmicro.com> References: <20110207152132.GM10564@opensource.wolfsonmicro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: Stephen Rothwell , linux-embedded@vger.kernel.org, Len Brown , Dmitry Torokhov , linux-kernel@vger.kernel.org, "Rafael J. Wysocki" , Geert Uytterhoeven , linux-pm@lists.linux-foundation.org, ppc-dev , Andrew Morton List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Feb 07, 2011 at 10:36:31AM -0500, Alan Stern wrote: > On Mon, 7 Feb 2011, Mark Brown wrote: > > I'd not be so sure - since it's a bool without an explicit default set > > Kconfig will default to disabling it and if anything enabling it is the > > option that requires special effort. > This may be a naive suggestion, but have you considered simply _asking_ > the people who added those defconfigs? I'm rather hoping that they'll notice the mailing list thread or that someone else who knows what's going on with them does - as Geert pointed out there's a considerable number of defconfigs that have this turned off. It seems more sensible to get some idea if this seems sane to people in the general case before going trying to identify and contact so many individuals. If there are systems that really require disabling CONFIG_PM we probably need to add stuff to Kconfig to make sure it can't be enabled anyway; this shouldn't enable any new configurations.