Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756497AbXFWA0m (ORCPT ); Fri, 22 Jun 2007 20:26:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753138AbXFWA0d (ORCPT ); Fri, 22 Jun 2007 20:26:33 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:3274 "EHLO scrub.xs4all.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755603AbXFWA0b (ORCPT ); Fri, 22 Jun 2007 20:26:31 -0400 Date: Sat, 23 Jun 2007 02:26:43 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Satyam Sharma cc: Trent Piepho , Mauro Carvalho Chehab , toralf.foerster@gmx.de, Oliver Neukum , LKML , Jan Engelhardt , Luca Risolia Subject: Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c In-Reply-To: Message-ID: References: <200706211117.55908.toralf.foerster@gmx.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 896 Lines: 23 Hi, On Sat, 23 Jun 2007, Satyam Sharma wrote: > But why? Let it do just one thing, and do it well. Is their > any requirement anywhere that requires us to give a dual > meaning to these menuconfig objects -- i.e. to also control > the inclusion / exclusion of code from the kernel as well as > also for the presentation + user interface purpose that it > currently serves? This getting ridiculous. :-( You're the one who is attaching a new meaning to it. Any config symbol has multiple meanings depending on the context, the menu property only changes _one_ of them, you want to drastically redefine it and that's not going to happen. bye, Roman - 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/