From: Julian Braha <julianbraha@gmail.com>
To: Nathan Chancellor <nathan@kernel.org>,
Andrew Jones <andrew.jones@linux.dev>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
nsc@kernel.org, andriy.shevchenko@linux.intel.com
Subject: Re: [PATCH] kconfig: add kconfig-sym-check static checker
Date: Thu, 14 May 2026 16:26:42 +0100 [thread overview]
Message-ID: <6d11bbb5-4877-4707-9f98-1b6ba2744ce8@gmail.com> (raw)
In-Reply-To: <177876553250.305249.17848321995033732158.b4-review@b4>
On 5/14/26 14:32, Nathan Chancellor wrote:
> On Wed, 13 May 2026 16:03:29 -0500, Andrew Jones <andrew.jones@linux.dev> wrote:
>
> Hi Andrew,
>
>> [...]
>>
>> This new static checker is the script used for [1] with a few
>> improvements to avoid some false positives.
>>
>> Link: https://bugzilla.kernel.org/show_bug.cgi?id=216748 [1]
>> Signed-off-by: Andrew Jones <andrew.jones@linux.dev>
>
> I think something like this is reasonable, as least until kconfirm
> is potentially ready for integration into the tree.
>
> https://lore.kernel.org/20260509203808.1142311-1-julianbraha@gmail.com/
>
Agreed, don't let kconfirm block this. While I do have future plans to
support these same alarms in that tool, there's currently no overlap
between these two, and no ETA on that support either ;)
Side note, this script was actually part of my inspiration to go
searching for more misusage of kconfig and build kconfirm. I also
previously cleaned up some dead code, thanks to this script:
https://lore.kernel.org/all/20260309122321.1528622-1-julianbraha@gmail.com/
- Julian Braha
next prev parent reply other threads:[~2026-05-14 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 21:03 [PATCH] kconfig: add kconfig-sym-check static checker Andrew Jones
2026-05-13 21:44 ` Andy Shevchenko
2026-05-13 23:31 ` Randy Dunlap
2026-05-14 13:32 ` Nathan Chancellor
2026-05-14 13:51 ` Andrew Jones
2026-05-14 15:26 ` Julian Braha [this message]
2026-05-14 16:01 ` 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=6d11bbb5-4877-4707-9f98-1b6ba2744ce8@gmail.com \
--to=julianbraha@gmail.com \
--cc=andrew.jones@linux.dev \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.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