[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0705080421540.13343@localhost.localdomain>
Date: Tue, 8 May 2007 04:27:13 -0400 (EDT)
From: "Robert P. J. Day" <rpjday@...dspring.com>
To: Thomas Gleixner <tglx@...utronix.de>
cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH][RFC] Create a top-level "Space-critical features" menu.
On Tue, 8 May 2007, Thomas Gleixner wrote:
> On Tue, 2007-05-08 at 04:06 -0400, Robert P. J. Day wrote:
> > i've always hated that lower-level menu under "General setup":
>
> Good reason to break everything which depends on CONFIG_EMBEDDED.
>
> tglx
>
> > -menuconfig EMBEDDED
> > - bool "Configure standard kernel features (for small systems)"
i don't know what you're getting at here. are you saying this is a
bad idea because it will make a mess of the current usage of
CONFIG_EMBEDDED in the source tree?
$ grep -rw CONFIG_EMBEDDED *
... lots of irrelevant defconfig output deleted ...
drivers/pci/setup-res.c:#ifdef CONFIG_EMBEDDED
include/linux/ide.h:#if !defined(MAX_HWIFS) || defined(CONFIG_EMBEDDED)
$
i don't see a whole lot of impact here. more to the point, though,
the word "EMBEDDED" in this context is just wrong. people might have
*other* reasons to de-activate some of those features rather than just
for an embedded system.
granted, that's probably where it will *mostly* happen, but i prefer
the idea of labelling those selections for what they really are -- for
*saving* *space*, because that's exactly what they represent.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
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