From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Jones <andrew.jones@linux.dev>
Cc: andriy.shevchenko@linux.intel.com, julianbraha@gmail.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
nathan@kernel.org, nsc@kernel.org, rdunlap@infradead.org,
tfiga@chromium.org, senozhatsky@chromium.org
Subject: Re: [PATCH v4] kconfig: add kconfig-sym-check static checker
Date: Tue, 23 Jun 2026 16:49:13 +0900 [thread overview]
Message-ID: <ajo4DVWoSaEZtBDa@google.com> (raw)
Hi,
Wasn't on the Cc list, hopefully I didn't mess up the headers.
Just saw this on LWN:
[..]
> + @echo ' kconfig-sym-check - Check for dangling Kconfig symbol references'
>
> +kconfig-sym-check:
> + $(Q)$(PERL) $(srctree)/scripts/kconfig/kconfig-sym-check.pl $(srctree) $(KCONFIG_SYM_CHECK_EXCLUDES)
I wonder if you have seen KCONFIG_WARN_UNKNOWN_SYMBOLS which seem
to be addressing the same (or very similar) problem (unless I'm missing
something).
Basically, what I have in my build script is
# perform kconfig symbol lookups: handles renamed, removed, etc. symbols
export KCONFIG_WARN_UNKNOWN_SYMBOLS=1
# make kconfig symbol lookup warnings fatal
export KCONFIG_WERROR=1
And then make fails whenever .config has something that is not
supposed to be there anymore. E.g.
.config:1606:warning: unknown symbol: SENSORS_APDS990X
.config:2498:warning: unknown symbol: APPLICOM
make[3]: *** [scripts/kconfig/Makefile:85: syncconfig] Error 1
make[2]: *** [Makefile:760: syncconfig] Error 2
next reply other threads:[~2026-06-23 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 7:49 Sergey Senozhatsky [this message]
2026-06-23 15:18 ` [PATCH v4] kconfig: add kconfig-sym-check static checker Andrew Jones
2026-06-23 15:25 ` Julian Braha
2026-06-23 16:10 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2026-05-27 14:27 Andrew Jones
2026-06-02 13:05 ` Nicolas Schier
2026-06-09 23:46 ` Nathan Chancellor
2026-06-10 16:00 ` Andrew Jones
2026-06-10 22:49 ` Nathan Chancellor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ajo4DVWoSaEZtBDa@google.com \
--to=senozhatsky@chromium.org \
--cc=20260527142703.107110-1-andrew.jones@linux.dev \
--cc=andrew.jones@linux.dev \
--cc=andriy.shevchenko@linux.intel.com \
--cc=julianbraha@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=rdunlap@infradead.org \
--cc=tfiga@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox