build-whitelist: do not add new options to whitelist when update
authorMasahiro Yamada <yamada.masahiro@socionext.com>
Mon, 26 Sep 2016 02:52:28 +0000 (11:52 +0900)
committerTom Rini <trini@konsulko.com>
Fri, 7 Oct 2016 14:26:30 +0000 (14:26 +0000)
commit9608f43c3d40d6ac6a1ea31e790d7cb863d58a3f
tree67994101d31efc9f265bd830f7ef5590a995cd20
parent03ab5d136b43296b2eb7d4dd80196381aa719a09
build-whitelist: do not add new options to whitelist when update

If somebody adds references to new CONFIG options in source files,
they will be added in the whitelist when we sync it.  (For example,
if we run scripts/build-whitelist.sh against commit 42f75050667b,
new options CONFIG_SPL_DFU_SUPPORT and CONFIG_USB_XHCI_UNIPHIER will
appear in the list.)

In order to make steady progress of Kconfig migration, we want to
only decrease whitelist options, but never increase.

So, when we update the whitelist, we should create a temporary list,
then take the intersection of the temporary one and the current one.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
scripts/build-whitelist.sh