u-boot.git/scripts/check-config.sh, branch v2017.09 Unnamed repository; edit this file 'description' to name the repository. scripts: config_whitelist: Handle lines with leading spaces/tabs 2017-06-29T14:01:10+00:00 Bin Meng bmeng.cn@gmail.com 2017-06-29T03:36:25+00:00 1f54a47ca1720a9b50a4ea59f263fc95eb1f89ea Some Kconfig options are defined in a line with leading spaces/tabs. Update build-whitelist/check-config scripts to handle such cases. Generate a new config_whitelist.txt with new scripts. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> 
Some Kconfig options are defined in a line with leading spaces/tabs.
Update build-whitelist/check-config scripts to handle such cases.
Generate a new config_whitelist.txt with new scripts.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
kbuild: beautify the log of config whitelist check 2017-02-08T20:56:30+00:00 Masahiro Yamada yamada.masahiro@socionext.com 2017-01-31T11:11:33+00:00 1bdd942b6da8a9e8686defe431380754cccb9b5a Use the kbuild style log. Prior to this commit: ./scripts/check-config.sh u-boot.cfg \ ./scripts/config_whitelist.txt . 1>&2 With this commit: CFGCHK u-boot.cfg Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Use the kbuild style log.

Prior to this commit:

./scripts/check-config.sh u-boot.cfg \
	./scripts/config_whitelist.txt . 1>&2

With this commit:

  CFGCHK  u-boot.cfg

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
check-config: fix wrong comment about how to build whitelist 2016-10-07T14:26:32+00:00 Masahiro Yamada yamada.masahiro@socionext.com 2016-09-26T04:04:58+00:00 7b76daab477264644b8c2dad78ccc9602c250251 The command suggested in this comment block is wrong; it would not rip off CONFIG options that had already been converted to Kconfig. Instead, we should use the scripts/build-whitelist.sh tool. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
The command suggested in this comment block is wrong; it would not
rip off CONFIG options that had already been converted to Kconfig.

Instead, we should use the scripts/build-whitelist.sh tool.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Makefile: Give a build error if ad-hoc CONFIG options are added 2016-09-16T21:27:24+00:00 Simon Glass sjg@chromium.org 2016-09-14T03:44:07+00:00 371244cb19f9804711dd66e4281ff7979915fd2e New CONFIG options should be added via Kconfig. To help prevent new ad-hoc CONFIGs from being added, give a build error when these are detected. Signed-off-by: Simon Glass <sjg@chromium.org> Acked-by: Stephen Warren <swarren@nvidia.com> Tested-by: Stephen Warren <swarren@nvidia.com> 
New CONFIG options should be added via Kconfig. To help prevent new ad-hoc
CONFIGs from being added, give a build error when these are detected.

Signed-off-by: Simon Glass <sjg@chromium.org>
Acked-by: Stephen Warren <swarren@nvidia.com>
Tested-by: Stephen Warren <swarren@nvidia.com>