[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1f2376e39dc46772e630e2cc9f9b40a2ef20993d@intel.com>
Date: Wed, 10 Dec 2025 17:07:39 +0200
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Nathan Chancellor <nathan@...nel.org>, Arnd Bergmann <arnd@...db.de>
Cc: Graham Roff <grahamr@....qualcomm.com>, Nicolas Schier <nsc@...nel.org>,
Jonathan Corbet <corbet@....net>, linux-kbuild@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, Nicolas Pitre
<nico@...xnic.net>
Subject: Re: [PATCH v2] Support conditional deps using "depends on X if Y"
On Fri, 05 Dec 2025, Nathan Chancellor <nathan@...nel.org> wrote:
> On Fri, Dec 05, 2025 at 09:01:51AM +0100, Arnd Bergmann wrote:
>> This is the bit that frequently confuses developers with the
>> current syntax, and I agree it would be nice to have a better
>> way, but I'm not sure the proposal actually helps enough to
>> warrant a mass-conversion of existing Kconfig files.
>
> I do agree that the 'depends on A || !A' syntax is confusing and that
> this does not really address that but I think that is besides the point
> here. I also agree that it is probably not worth converting existing
> users to this syntax (unless there is solid reasoning), I would not want
> to see cleanup patches of that nature, just use in new code.
I think "depends on A if A" is an improvement over "A || !A". But not a
drastic improvement.
I think the question is, can we figure out an even better syntax for
that use case? Something that conveys the "optionally depends on A"
meaning? Is there something so good that it would warrant cleanup
conversions just for the improved clarity?
If we can't come up with anything, let's just roll with what we have
here?
BR,
Jani.
--
Jani Nikula, Intel
Powered by blists - more mailing lists