[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <19f6c99dfcc2a9c2ca4c43ba0ad352fc978c1cc9@intel.com>
Date: Fri, 05 Dec 2025 11:06:56 +0200
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Graham Roff <grahamr@....qualcomm.com>, Nathan Chancellor
<nathan@...nel.org>, Nicolas Schier <nsc@...nel.org>, Jonathan Corbet
<corbet@....net>
Cc: linux-kbuild@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, Nicolas Pitre <nico@...xnic.net>, Graham
Roff <grahamr@....qualcomm.com>
Subject: Re: [PATCH v2] Support conditional deps using "depends on X if Y"
On Tue, 18 Nov 2025, Graham Roff <grahamr@....qualcomm.com> wrote:
> @@ -602,8 +612,14 @@ Some drivers are able to optionally use a feature from another module
> or build cleanly with that module disabled, but cause a link failure
> when trying to use that loadable module from a built-in driver.
>
> -The most common way to express this optional dependency in Kconfig logic
> -uses the slightly counterintuitive::
> +The recommended way to express this optional dependency in Kconfig logic
> +uses the conditional form::
> +
> + config FOO
> + tristate "Support for foo hardware"
> + depends on BAR if BAR
> +
> +This slightly counterintuitive style is also widely used::
>
> config FOO
> tristate "Support for foo hardware"
Thanks for adding this documentation hunk.
BR,
Jani.
--
Jani Nikula, Intel
Powered by blists - more mailing lists