[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62a51b2e5425a3cca4f7a66e2795b957f237b2da.camel@mellanox.com>
Date: Tue, 21 Apr 2020 16:30:29 +0000
From: Saeed Mahameed <saeedm@...lanox.com>
To: "nico@...xnic.net" <nico@...xnic.net>
CC: "masahiroy@...nel.org" <masahiroy@...nel.org>,
"Laurent.pinchart@...asonboard.com"
<Laurent.pinchart@...asonboard.com>,
"airlied@...ux.ie" <airlied@...ux.ie>,
"jgg@...pe.ca" <jgg@...pe.ca>,
"linux-kbuild@...r.kernel.org" <linux-kbuild@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jernej.skrabec@...l.net" <jernej.skrabec@...l.net>,
"arnd@...db.de" <arnd@...db.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"jonas@...boo.se" <jonas@...boo.se>,
"jani.nikula@...ux.intel.com" <jani.nikula@...ux.intel.com>,
"kieran.bingham+renesas@...asonboard.com"
<kieran.bingham+renesas@...asonboard.com>,
"narmstrong@...libre.com" <narmstrong@...libre.com>,
"leon@...nel.org" <leon@...nel.org>
Subject: Re: [RFC PATCH 1/2] Kconfig: Introduce "uses" keyword
On Tue, 2020-04-21 at 09:58 -0400, Nicolas Pitre wrote:
> On Tue, 21 Apr 2020, Saeed Mahameed wrote:
>
> > I wonder how many of those 8889 cases wanted a weak dependency but
> > couldn't figure out how to do it ?
> >
> > Users of depends on FOO || !FOO
> >
> > $ git ls-files | grep Kconfig | xargs grep -E \
> > "depends\s+on\s+([A-Za-z0-9_]+)\s*\|\|\s*(\!\s*\1|\1\s*=\s*n)" \
> > | wc -l
> >
> > 156
> >
> > a new keyword is required :) ..
> >
> >
> > > In another mail I suggested
> > >
> > > optionally depends on FOO
> > >
> > > might be a better alternative than "uses".
> > >
> > >
> >
> > how about just:
> > optional FOO
> >
> > It is clear and easy to document ..
>
> I don't dispute your argument for having a new keyword. But the most
> difficult part as Arnd said is to find it. You cannot pretend that
kconfig-language.rst ?
> "optional FOO" is clear when it actually imposes a restriction when
> FOO=m. Try to justify to people why they cannot select y because of
> this
> "optional" thing.
>
Then let's use "uses" it is more assertive. Documentation will cover
any vague anything about it ..
>
> Nicolas
Powered by blists - more mailing lists