<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/scripts/check-config.sh, branch v2017.09-rc2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/scripts/check-config.sh?h=v2017.09-rc2</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/scripts/check-config.sh?h=v2017.09-rc2'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2017-06-29T14:01:10Z</updated>
<entry>
<title>scripts: config_whitelist: Handle lines with leading spaces/tabs</title>
<updated>2017-06-29T14:01:10Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2017-06-29T03:36:25Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1f54a47ca1720a9b50a4ea59f263fc95eb1f89ea'/>
<id>urn:sha1:1f54a47ca1720a9b50a4ea59f263fc95eb1f89ea</id>
<content type='text'>
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 &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>kbuild: beautify the log of config whitelist check</title>
<updated>2017-02-08T20:56:30Z</updated>
<author>
<name>Masahiro Yamada</name>
<email>yamada.masahiro@socionext.com</email>
</author>
<published>2017-01-31T11:11:33Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1bdd942b6da8a9e8686defe431380754cccb9b5a'/>
<id>urn:sha1:1bdd942b6da8a9e8686defe431380754cccb9b5a</id>
<content type='text'>
Use the kbuild style log.

Prior to this commit:

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

With this commit:

  CFGCHK  u-boot.cfg

Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>check-config: fix wrong comment about how to build whitelist</title>
<updated>2016-10-07T14:26:32Z</updated>
<author>
<name>Masahiro Yamada</name>
<email>yamada.masahiro@socionext.com</email>
</author>
<published>2016-09-26T04:04:58Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7b76daab477264644b8c2dad78ccc9602c250251'/>
<id>urn:sha1:7b76daab477264644b8c2dad78ccc9602c250251</id>
<content type='text'>
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 &lt;yamada.masahiro@socionext.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>Makefile: Give a build error if ad-hoc CONFIG options are added</title>
<updated>2016-09-16T21:27:24Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-09-14T03:44:07Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=371244cb19f9804711dd66e4281ff7979915fd2e'/>
<id>urn:sha1:371244cb19f9804711dd66e4281ff7979915fd2e</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
Acked-by: Stephen Warren &lt;swarren@nvidia.com&gt;
Tested-by: Stephen Warren &lt;swarren@nvidia.com&gt;
</content>
</entry>
</feed>
