Messages in this thread | | | Date | Mon, 31 Jan 2005 20:18:58 -0800 | From | Matt Mackall <> | Subject | Re: [PATCH 0/8] base-small: CONFIG_BASE_SMALL for small systems |
| |
On Mon, Jan 31, 2005 at 09:55:32PM -0300, Horst von Brand wrote: > Matt Mackall <mpm@selenic.com> said: > > This patch series introduced a new pair of CONFIG_EMBEDDED options call > > CONFIG_BASE_FULL/CONFIG_BASE_SMALL. Disabling CONFIG_BASE_FULL sets > > the boolean CONFIG_BASE_SMALL to 1 and it is used to shrink a number > > of core data structures. The space savings for the current batch is > > around 14k. > > Why _two_ config options?
Um, Andrew made me do it?
One option is an int and is used thusly:
#define FOO (CONFIG_BASE_SMALL ? 1 : 1000)
But it's also sometimes useful to have two opposing options so that you can use:
obj-(CONFIG_OBJ_A) += a.obj obj-(CONFIG_OBJ_B) += b.obj
-- Mathematics is the supreme nostalgia of our time. - 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/
| |