Skip to content

Commit b50b8ac

Browse files
ulfalizernashif
authored andcommitted
check_compliance: Set KCONFIG_WARN_UNDEF instead of KCONFIG_STRICT
They are synonyms, and KCONFIG_WARN_UNDEF is more explicit. KCONFIG_STRICT became a bad name when more env. variables warnings were added to control warnings, but it's still supported for backwards compatibility. Signed-off-by: Ulf Magnusson <[email protected]>
1 parent 179468f commit b50b8ac

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

scripts/ci/check_compliance.py

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -250,9 +250,9 @@ def parse_kconfig(self):
250250
# For multi repo support
251251
self.get_modules(os.path.join(tempfile.gettempdir(), "Kconfig.modules"))
252252

253-
# Enable strict Kconfig mode in Kconfiglib, which assumes there's just a
254-
# single Kconfig tree and warns for all references to undefined symbols
255-
os.environ["KCONFIG_STRICT"] = "y"
253+
# Tells Kconfiglib to generate warnings for all references to undefined
254+
# symbols within Kconfig files
255+
os.environ["KCONFIG_WARN_UNDEF"] = "y"
256256

257257
try:
258258
return kconfiglib.Kconfig()

0 commit comments

Comments
 (0)