10408 2016-10-10 21:53:27 +0000 kernel_configcheck shouldn't complain when an "is not set" is requested and the actual value is a blank in the final config 2016-11-02 18:24:10 +0000 1 1 6 Yocto Project Subprojects Kernel kernel-tooling 2.2 x86 Multiple RESOLVED NOTABUG Undecided normal --- 10426 1 california.l.sullivan bruce.ashfield yp.kernel.watcher yp.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 67108 0 california.l.sullivan 2016-10-10 21:53:27 +0000 I started out trying to fix this in the in the intel-corei7-64-preempt-rt BSP: Requested value: CONFIG_LEDS_TRIGGER_CPU=y Actual value: I added "# CONFIG_LEDS_TRIGGER_CPU is not set" to a new preempt-rt blacklist feature that turns off things that depend on !PREEMPT_RT_* options, but unfortunately I now get the following: Requested value: # CONFIG_LEDS_TRIGGER_CPU is not set Actual value: As far as I know, the resulting kernel should be the same whether an option is completely missing or shown as "is not set", so we probably should not throw a warning in this case. 67118 1 bruce.ashfield 2016-10-11 02:33:40 +0000 This is a valid warning. If an option is turned off because it is a valid tristate that has been disabled, the other is a value that has been hidden by a wrapping config option. One needs to be set, the other doesn't.