Browse Source

scripts: ci: check_compliance: allow Kconfig references with '(' and '.'

For regexes such as `CONFIG_DEBUG_(OPTIMIZATIONS|INFO)` and
to be able to use `.*` as this syntax is used in the Kconfig search.

Signed-off-by: Tomi Fontanilles <tomi.fontanilles@nordicsemi.no>
pull/77257/head
Tomi Fontanilles 11 months ago committed by Anas Nashif
parent
commit
4ea0e88687
  1. 4
      scripts/ci/check_compliance.py

4
scripts/ci/check_compliance.py

@ -838,7 +838,7 @@ Missing SoC names or CONFIG_SOC vs soc.yml out of sync: @@ -838,7 +838,7 @@ Missing SoC names or CONFIG_SOC vs soc.yml out of sync:
undef_to_locs = collections.defaultdict(list)
# Warning: Needs to work with both --perl-regexp and the 're' module
regex = r"\bCONFIG_[A-Z0-9_]+\b(?!\s*##|[$@{*])"
regex = r"\bCONFIG_[A-Z0-9_]+\b(?!\s*##|[$@{(.*])"
# Skip doc/releases and doc/security/vulnerabilities.rst, which often
# reference removed symbols
@ -881,7 +881,7 @@ If the reference is for a comment like /* CONFIG_FOO_* */ (or @@ -881,7 +881,7 @@ If the reference is for a comment like /* CONFIG_FOO_* */ (or
/* CONFIG_FOO_*_... */), then please use exactly that form (with the '*'). The
CI check knows not to flag it.
More generally, a reference followed by $, @, {{, *, or ## will never be
More generally, a reference followed by $, @, {{, (, ., *, or ## will never be
flagged.
{undef_desc}""")

Loading…
Cancel
Save