Prev: [PATCH 1/4] kconfig: save location of config symbols
Next: [PATCH 2/4] kconfig: print more info when we see a recursive dependency
From: Sam Ravnborg on 25 Jul 2010 17:40
After reading some of the mails about the
defconfig files I decided to take a look at kconfig.
We already decided to go for a solution where the defconfig
files contains only the minimal configuration.
Uwe developed a script to assist but having native support
in kconfig is preferable.
This patch set introduce "alldefconfig".
alldefconfig create a configuration with all values set
to default values.
This can be usefull when we check if we do have a sane
set of default values. Rhe config can be inspected
The patches also introduce "savedefconfig" which
reads the current configuration and save it
as a minimal configuration.
In my testing I benchmarked it with one
of the arm defconfings and the final result is
the same (symbols appear in different order).
The first two patches is not relevant to the above.
They was just stuff I had pending.
The patches has seen only light testing for now,
and any feedback is welcome.
After finishing off these patches I will take a closer
look at the patch form Stephen that introduce
a more advanced select.
Note: Anyone that have heard from Roman Zippel recently?
Roman Zippel (1):
kconfig: print more info when we see a recursive dependency
Sam Ravnborg (3):
kconfig: save location of config symbols
kconfig: add alldefconfig
kconfig: add savedefconfig
Documentation/kbuild/kconfig.txt | 2 +-
scripts/kconfig/Makefile | 13 ++-
scripts/kconfig/conf.c | 46 ++++++--
scripts/kconfig/confdata.c | 94 +++++++++++++++
scripts/kconfig/expr.h | 1 +
scripts/kconfig/lkc.h | 2 +
scripts/kconfig/lkc_proto.h | 1 +
scripts/kconfig/menu.c | 2 +
scripts/kconfig/symbol.c | 242 +++++++++++++++++++++++++++++++++++---
9 files changed, 373 insertions(+), 30 deletions(-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/