[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200417140750.GF26002@ziepe.ca>
Date: Fri, 17 Apr 2020 11:07:50 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Jani Nikula <jani.nikula@...ux.intel.com>
Cc: Saeed Mahameed <saeedm@...lanox.com>,
Masahiro Yamada <masahiroy@...nel.org>,
linux-kbuild@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
Nicolas Pitre <nico@...xnic.net>, narmstrong@...libre.com,
Laurent.pinchart@...asonboard.com, leon@...nel.org,
kieran.bingham+renesas@...asonboard.com, jonas@...boo.se,
airlied@...ux.ie, jernej.skrabec@...l.net,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org, Andrzej Hajda <a.hajda@...sung.com>
Subject: Re: [RFC PATCH 1/2] Kconfig: Introduce "uses" keyword
On Fri, Apr 17, 2020 at 05:01:18PM +0300, Jani Nikula wrote:
> On Fri, 17 Apr 2020, Jason Gunthorpe <jgg@...pe.ca> wrote:
> > On Fri, Apr 17, 2020 at 09:23:59AM +0300, Jani Nikula wrote:
> >
> >> Which means that would have to split up to two. Not ideal, but
> >> doable.
> >
> > Why is this not ideal?
> >
> > I think the one per line is easier to maintain (eg for merge
> > conflicts) and easier to read than a giant && expression.
> >
> > I would not complicate things further by extending the boolean
> > language..
>
> Fair enough. I only found one instance where the patch at hand does not
> cut it:
>
> drivers/hwmon/Kconfig: depends on !OF || IIO=n || IIO
Ideally this constraint would be expressed as:
optionally depends on OF && IIO
And if the expression is n then IIO is not prevented from being y.
Ie the code is just doing:
#if defined(CONFIG_OF) && IS_ENABLED(CONFIG_IIO)
Jason
Powered by blists - more mailing lists