Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932515AbWAFRfx (ORCPT ); Fri, 6 Jan 2006 12:35:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964806AbWAFRfx (ORCPT ); Fri, 6 Jan 2006 12:35:53 -0500 Received: from mailout.stusta.mhn.de ([141.84.69.5]:59660 "HELO mailout.stusta.mhn.de") by vger.kernel.org with SMTP id S932515AbWAFRfw (ORCPT ); Fri, 6 Jan 2006 12:35:52 -0500 Date: Fri, 6 Jan 2006 18:35:47 +0100 From: Adrian Bunk To: Andrew Morton Cc: linux-kernel@vger.kernel.org Subject: [2.6 patch] don't allow users to set CONFIG_BROKEN=y Message-ID: <20060106173547.GR12131@stusta.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1270 Lines: 44 Do not allow people to create configurations with CONFIG_BROKEN=y. The sole reason for CONFIG_BROKEN=y would be if you are working on fixing a broken driver, but in this case editing the Kconfig file is trivial. Never ever should a user enable CONFIG_BROKEN. Signed-off-by: Adrian Bunk --- This patch was already sent on: - 13 Dec 2005 --- linux-2.6.15-rc5-mm2-full/init/Kconfig.old 2005-12-13 18:48:40.000000000 +0100 +++ linux-2.6.15-rc5-mm2-full/init/Kconfig 2005-12-13 18:48:52.000000000 +0100 @@ -31,19 +31,8 @@ you say Y here, you will be offered the choice of using features or drivers that are currently considered to be in the alpha-test phase. -config CLEAN_COMPILE - bool "Select only drivers expected to compile cleanly" if EXPERIMENTAL - default y - help - Select this option if you don't even want to see the option - to configure known-broken drivers. - - If unsure, say Y - config BROKEN bool - depends on !CLEAN_COMPILE - default y config BROKEN_ON_SMP bool - 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/