From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Tue, 27 Sep 2016 13:44:44 -0400 Subject: [U-Boot] [PATCH 5/5] check-config: allow to complete build even with ad-hoc CONFIG options In-Reply-To: <1474862702-16580-6-git-send-email-yamada.masahiro@socionext.com> References: <1474862702-16580-1-git-send-email-yamada.masahiro@socionext.com> <1474862702-16580-6-git-send-email-yamada.masahiro@socionext.com> Message-ID: <20160927174444.GK4884@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: