[Bugfix]Kconfig:ensure compatibility between kconfig-frontend and kconfiglib in kernel build #13532
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
After #13452 this commit, the three-state
<m>in kernel mode cannot be selected when using kconfig-frontendBecause kconfiglib recognizes
MODULEconfiguration but notmodulesattributes,and kconfig-frontend is compatible with the latest
modulesattributes of Linux,we can only use the old version to use
MODULEconfiguration PLUSoptions modulesto be compatible with both.Impact
this is a patch for #13452
Testing
qemu-armv8a:knsh with kconfig-frontend
qemu-armv8a:knsh with kconfiglib