Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Julian Braha <julianbraha@gmail.com>
Cc: Andrew Jones <andrew.jones@linux.dev>,
	 Sergey Senozhatsky <senozhatsky@chromium.org>,
	andriy.shevchenko@linux.intel.com, linux-kbuild@vger.kernel.org,
	 linux-kernel@vger.kernel.org, nathan@kernel.org, nsc@kernel.org,
	rdunlap@infradead.org,  tfiga@chromium.org
Subject: Re: [PATCH v4] kconfig: add kconfig-sym-check static checker
Date: Wed, 24 Jun 2026 12:29:40 +0900	[thread overview]
Message-ID: <ajtOv5l8nIWS-WeH@google.com> (raw)
In-Reply-To: <f2520b56-59d8-45d1-8f38-90f2472c96e9@gmail.com>

Hi,

On (26/06/23 16:25), Julian Braha wrote:
> >> 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).
> 
> > Thanks, Sergey. I wasn't aware of this. Is there a way to combine that
> 
> The two tools do not do the same thing. One is a check on .config and
> the other is a check on the Kconfig spec.

Ah, I see.  I didn't check the code, obviously.

  parent reply	other threads:[~2026-06-24  3:29 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 [this message]
2026-06-24  3:27   ` Sergey Senozhatsky
2026-06-24  3:34     ` Sergey Senozhatsky
  -- 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=ajtOv5l8nIWS-WeH@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