mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Nathan Chancellor <nathan@kernel.org>,
	Graham Roff <grahamr@qti.qualcomm.com>
Cc: Nicolas Schier <nsc@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>
Subject: Re: [PATCH] Support conditional deps using "depends on X if Y"
Date: Mon, 10 Nov 2025 10:48:59 +0200	[thread overview]
Message-ID: <82317993284703834a7b1d8d5ca05b7c646f2795@intel.com> (raw)
In-Reply-To: <20251109232922.GA2977577@ax162>

On Sun, 09 Nov 2025, Nathan Chancellor <nathan@kernel.org> wrote:
> I think it would be useful to have a slightly more concrete example in
> the documentation of where this could be useful because even with the
> "if" syntax, it still feels a little confusing to me at least with the
> current example. Since this is just internally converting "depends on A
> if B" to "depends on A || !B", this seems like a low risk addition to
> the Kconfig language but it would be good to have some tests under
> scripts/kconfig/tests like the ones recently added by commit
> f9afce4f32e9 ("kconfig: Add transitional symbol attribute for migration
> support") upstream.

"depends on A || !A" (or A=n) is the most common pattern in Kconfig,
which literally means "depends on A if A".

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-11-10  8:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-08  1:16 Graham Roff
2025-11-09 23:29 ` Nathan Chancellor
2025-11-10  8:48   ` Jani Nikula [this message]
2025-11-10 21:15     ` Nathan Chancellor
2025-11-10 22:32       ` Randy Dunlap
2025-11-11  4:09         ` Graham Roff
2025-11-11  7:06       ` Jani Nikula
2025-11-11 22:21         ` Graham Roff

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=82317993284703834a7b1d8d5ca05b7c646f2795@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=grahamr@qti.qualcomm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=nico@fluxnic.net \
    --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

all inboxes | Powered by JetHome®