Messages in this thread | | | Date | Wed, 14 Apr 2004 09:31:50 -0400 | From | Chris Friesen <> | Subject | Re: [PATCH] conditionalize some boring buffer_head checks |
| |
Jeff Garzik wrote: > Tim Hockin wrote: > >> Somewhat off the original topic, but am I the only one who finds it weird >> (and error-prone) that you have to add the same KConfig to a dozen or >> more >> Kconfig files? >> >> Shouldn't there be a KConfig libe, and all you need to do for the arch is >> reference the CONFIG_FOO from the lib? Would at least save all the >> duplicate strings and definitions...
> Seems a lot easier just to gather the common definitions into a Kconfig > file, and include it via the standard 'source' directive.
Either way, I personally would be extremely grateful for some kind of standard way to add a new configurable generic feature to every architecture. I'm tired of having to add it manually. I hadn't realized about the "source" feature--seems like we should be able to pull a lot of stuff into something like that even now.
On a side note, why is there no Kconfig for the "kernel" directory?
Chris - 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/
| |