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? -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
