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: Wed, 24 Jun 2026 12:34:21 +0900 [thread overview]
Message-ID: <ajtPk6gz8bd4bsxy@google.com> (raw)
In-Reply-To: <ajtM3i49HcYAF3wX@google.com>
On (26/06/24 12:27), Sergey Senozhatsky wrote:
> % echo "CONFIG_DISABLE_BUGS=y" >> .config
>
> - Now run make (KCONFIG_WARN_UNKNOWN_SYMBOLS/KCONFIG_WERROR are env
> variables)
>
> % KCONFIG_WARN_UNKNOWN_SYMBOLS=1 KCONFIG_WERROR=1 make oldconfig
>
> .config:4693:warning: unknown symbol: DISABLE_BUGS
> make[2]: *** [scripts/kconfig/Makefile:85: oldconfig] Error 1
> make[1]: *** [/media/dev/linux/Makefile:760: oldconfig] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
>
> And make fails.
>
> kconfig reads the symbols for (pretty much?) all the targets, it
> needs to make sure that nothing is missing (SAT), that there are
> no conflicts and so on. Detecting unrecognized .config symbols
> on the kconfig level is a low hanging fruit, in this regard.
OK, maybe they are not similar, as Julian pointed out. Makes
we wonder is there any benefit in moving this functionality
into kconfig (which is the tool that deals with Kconfig files).
next prev parent reply other threads:[~2026-06-24 3:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 7:49 [PATCH v4] kconfig: add kconfig-sym-check static checker Sergey Senozhatsky
2026-06-23 15:18 ` Andrew Jones
2026-06-23 15:25 ` Julian Braha
2026-06-23 16:10 ` Andy Shevchenko
2026-06-24 3:29 ` Sergey Senozhatsky
2026-06-24 3:27 ` Sergey Senozhatsky
2026-06-24 3:34 ` Sergey Senozhatsky [this message]
-- 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=ajtPk6gz8bd4bsxy@google.com \
--to=senozhatsky@chromium.org \
--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