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.


Masahiro Yamada (3):
  build-whitelist: do not add new options to whitelist when update
  config_whitelist: sync by tool
  config_whitelist: remove bogus options

 scripts/build-whitelist.sh   | 15 +++++++++++++--
 scripts/config_whitelist.txt | 16 ----------------
 2 files changed, 13 insertions(+), 18 deletions(-)

-- 
1.9.1

_______________________________________________
U-Boot mailing list
[email protected]
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to