Hi, We found that the Kconfig build system silently changes invalid values in the. config file, which may prevent users from getting their desired kernel, and also make it hard to know which configuration option caused the forced change based on the compilation information. There are similar questions on stack overflow, where people find it difficult to get the complete dependency chain and other information： ex1. How can I disable CONFIG_PM when building Linux kernel for x86_64 - Stack Overflow https://stackoverflow.com/questions/64499221/how-can-i-disable-config-pm-when-building-linux-kernel-for-x86-64/64501647#64501647 ex2. c - kernel symbol enabled but doesn't shows up in .config - Stack Overflow https://stackoverflow.com/questions/24074116/kernel-symbol-enabled-but-doesnt-shows-up-in-config) ex3. makefile - update menuconfig entries without recompiling all the kernel - Stack Overflow https://stackoverflow.com/questions/71075113/update-menuconfig-entries-without-recompiling-all-the-kernel ex4. linux - disabling CONFIG_NET_DMA - Stack Overflow https://stackoverflow.com/questions/30794576/disabling-config-net-dma/30796820#30796820 We plan to optimize the conf_read() function in /scripts/kconfig/confdata.c, and add information for the mismatched configuration options to help users get the desired Linux kernel. Do you think it's necessary? Any suggestions? Best regards, Siyuan Guo Ying Sun
