public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Julian Braha <julianbraha@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	akpm@linux-foundation.org, ljs@kernel.org
Cc: arnd@arndb.de, gregkh@linuxfoundation.org, masahiroy@kernel.org,
	nathan@kernel.org, nsc@kernel.org, ojeda@kernel.org,
	corbet@lwn.net, linux-kernel@vger.kernel.org,
	rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kbuild@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] Documentation: dev-tools: add kconfirm
Date: Tue, 28 Apr 2026 19:06:40 +0100	[thread overview]
Message-ID: <b5918621-08d2-4ad6-850f-dda18a1e774d@gmail.com> (raw)
In-Reply-To: <dcb7439832f0bb35598fba653d922b5f6a4d0058@intel.com>

On Tue, 28 Apr 2026, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> Oh, I'd really like a check on this part from kconfig-language.rst:
>
> i.e. warn on selecting visible symbols or symbols with
> dependencies.

Hi Jani,

This is very doable in the general case of unconditional
visibility/non-visibility. Handling the more complex case of conditional
prompts will require finishing the SMT model, coming later.

I'll add this check, hopefully for kconfirm v0.8 / RFC 2 :)

Thanks for the inspiration, and let me know if you have any other ideas,
too.

- Julian Braha

      reply	other threads:[~2026-04-28 18:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 17:44 [RFC PATCH 0/2] scripts: add kconfirm Julian Braha
2026-04-27 17:44 ` [RFC PATCH 1/2] " Julian Braha
2026-04-27 20:48   ` Greg KH
2026-04-28 21:17     ` Julian Braha
2026-04-28  7:01   ` Jonathan Corbet
2026-04-28 18:31     ` Nathan Chancellor
2026-04-28 19:08       ` Jonathan Corbet
2026-04-27 17:44 ` [RFC PATCH 2/2] Documentation: dev-tools: " Julian Braha
2026-04-27 18:17   ` Miguel Ojeda
2026-04-27 19:33     ` Arnd Bergmann
2026-04-28 11:51       ` Miguel Ojeda
2026-04-28 12:58         ` Gary Guo
2026-04-28 18:45         ` Nathan Chancellor
2026-04-29  0:38           ` Miguel Ojeda
2026-04-28 17:01       ` Julian Braha
2026-04-28  8:23   ` Jani Nikula
2026-04-28 18:06     ` Julian Braha [this message]

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=b5918621-08d2-4ad6-850f-dda18a1e774d@gmail.com \
    --to=julianbraha@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.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