Hi Tom, Simon, 2016-09-28 2:44 GMT+09:00 Tom Rini <tr...@konsulko.com>: > On Mon, Sep 26, 2016 at 01:05:02PM +0900, Masahiro Yamada wrote: > >> Currently, the check-config.sh terminates the build when unknown >> ad-hoc options are detected. I think it is too much because we may >> want to patch config headers locally in a build/deployment project. > > I'm not yet convinced this is a good use case. In the not-so-long-now > term include/configs/ should go away. So you wouldn't be able to do an > ad-hoc thing like this for testing. And tossing stuff ad-hoc into > $(BOARDDIR)/Kconfig should be easy enough too, yes? >
You are right. I tend to add local-hack options into my header file just because it is easier than creating Kconfig entries and enabling them from a defconfig, but it is possible to do so with a little more effort. So, I retract this patch and marked the Patchwork one as Rejected. -- Best Regards Masahiro Yamada _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
