Messages in this thread | | | Date | Wed, 28 Oct 2015 15:26:54 +0900 | From | Darren Hart <> | Subject | Re: [PATCH 05/10] merge_config.sh: Better handling of CONFIG_FOO=n |
| |
On Wed, Oct 28, 2015 at 09:42:06AM +0900, Olof Johansson wrote: > Kconfig knows how to handle CONFIG_FOO=n just fine, but it'll always > use "# CONFIG FOO is not set" in the resulting config. Mangle the input > accordingly so we don't report this as a failure when it isn't. > > Signed-off-by: Olof Johansson <olof@lixom.net>
Matching Kconfig behavior is the logical approach, no point in complaining if Kconfig will accpet the result.
Bruce, I think we'll just need to update the linux-yocto tool documentation not to mark =n as wrong.
Reviewed-by: Darren Hart <dvhart@linux.intel.com>
-- Darren Hart Intel Open Source Technology Center
| |