aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/bluetooth
diff options
context:
space:
mode:
authorSam Ravnborg <sam@ravnborg.org>2008-06-30 22:53:04 +0200
committerSam Ravnborg <sam@ravnborg.org>2008-07-25 22:12:50 +0200
commitcd9140e1e73a31fd45f1fd4585260643a2f9ab1d (patch)
tree8ece89eabe4f7e6b5e7638778125e4cb3e433a93 /drivers/bluetooth
parentf443d2eccf077afd8a839cc7ed66cc4d520c5f05 (diff)
downloadkernel_samsung_smdk4412-cd9140e1e73a31fd45f1fd4585260643a2f9ab1d.zip
kernel_samsung_smdk4412-cd9140e1e73a31fd45f1fd4585260643a2f9ab1d.tar.gz
kernel_samsung_smdk4412-cd9140e1e73a31fd45f1fd4585260643a2f9ab1d.tar.bz2
kconfig: make oldconfig is now less chatty
Previously when running "make oldconfig" we saw all the propmt lines from kconfig and noone actully read this. With this patch the user will only see output if there is new symbols. This will be seen as "make oldconfig" runs which does not generate any output. A typical run now looks like this: $ make oldconfig scripts/kconfig/conf -o arch/x86/Kconfig $ If a new symbol is found then we restart the config process like this: $ make oldconfig scripts/kconfig/conf -o arch/x86/Kconfig * * Restart config... * * * General setup * Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y Local version - append to kernel release (LOCALVERSION) [] ... The bahaviour is similar to what we know when running the implicit oldconfig target "make silentoldconfig". "make silentoldconfig" are run as part of the kernel build process if the configuration has changed. Signed-off-by: Sam Ravnborg <sam@ravnborg.org> Cc: Roman Zippel <zippel@linux-m68k.org>
Diffstat (limited to 'drivers/bluetooth')
0 files changed, 0 insertions, 0 deletions