The current build-whitelist.sh allows to add new options into the whitelist. For example, it is possible that somebody adds #ifdef CONFIG_NEW_OPTITON to his C file. So, the build-whitelist.sh will pick it up when we run it next time. We never want to increase the ad-hoc options. 1/2 bans such a case.
2/2 is optional. It is very easy to reproduce it. Masahiro Yamada (2): build-whitelist: do not add new options to whitelist when update Sync config_whitelist.txt scripts/build-whitelist.sh | 10 ++++++++-- scripts/config_whitelist.txt | 2 -- 2 files changed, 8 insertions(+), 4 deletions(-) -- 1.9.1 _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
