Bug 10408

Summary: kernel_configcheck shouldn't complain when an "is not set" is requested and the actual value is a blank in the final config
Product: [Yocto Project Subprojects] Kernel Reporter: California Sullivan <california.l.sullivan>
Component: kernel-toolingAssignee: Bruce Ashfield <bruce.ashfield>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: Undecided CC: yp.kernel.watcher, yp.watcher
Version: 2.2   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on:    
Bug Blocks: 10426    

Description California Sullivan 2016-10-10 21:53:27 UTC 
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.
Comment 1 Bruce Ashfield 2016-10-11 02:33:40 UTC 
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.