[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706230216140.1817@scrub.home>
Date: Sat, 23 Jun 2007 02:26:43 +0200 (CEST)
From: Roman Zippel <zippel@...ux-m68k.org>
To: Satyam Sharma <satyam.sharma@...il.com>
cc: Trent Piepho <xyzzy@...akeasy.org>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
toralf.foerster@....de, Oliver Neukum <oneukum@...e.de>,
LKML <linux-kernel@...r.kernel.org>,
Jan Engelhardt <jengelh@...ux01.gwdg.de>,
Luca Risolia <luca.risolia@...dio.unibo.it>
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
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists