Re: [PATCH 05/10] merge_config.sh: Better handling of CONFIG_FOO=n
From: Darren Hart
Date: Wed Oct 28 2015 - 02:27:16 EST
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@xxxxxxxxx>
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@xxxxxxxxxxxxxxx>
Intel Open Source Technology Center
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/