netdev - Re: [RFC 0/6] Regressions for "imply" behavior change

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <874ktj4tvn.fsf@intel.com>
Date:   Thu, 16 Apr 2020 13:17:32 +0300
From:   Jani Nikula <jani.nikula@...ux.intel.com>
To:     Arnd Bergmann <arnd@...db.de>, Saeed Mahameed <saeedm@...lanox.com>
Cc:     "narmstrong\@baylibre.com" <narmstrong@...libre.com>,
        "masahiroy\@kernel.org" <masahiroy@...nel.org>,
        "Laurent.pinchart\@ideasonboard.com" 
        <Laurent.pinchart@...asonboard.com>,
        "leon\@kernel.org" <leon@...nel.org>,
        "davem\@davemloft.net" <davem@...emloft.net>,
        "linux-renesas-soc\@vger.kernel.org" 
        <linux-renesas-soc@...r.kernel.org>,
        "linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
        "nico\@fluxnic.net" <nico@...xnic.net>,
        "linux-rdma\@vger.kernel.org" <linux-rdma@...r.kernel.org>,
        "dri-devel\@lists.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
        "kieran.bingham+renesas\@ideasonboard.com" 
        <kieran.bingham+renesas@...asonboard.com>,
        "a.hajda\@samsung.com" <a.hajda@...sung.com>,
        "jonas\@kwiboo.se" <jonas@...boo.se>,
        "netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
        "airlied\@linux.ie" <airlied@...ux.ie>,
        "jgg\@ziepe.ca" <jgg@...pe.ca>,
        "jernej.skrabec\@siol.net" <jernej.skrabec@...l.net>
Subject: Re: [RFC 0/6] Regressions for "imply" behavior change

On Thu, 16 Apr 2020, Arnd Bergmann <arnd@...db.de> wrote:
> On Thu, Apr 16, 2020 at 5:25 AM Saeed Mahameed <saeedm@...lanox.com> wrote:
>> BTW how about adding a new Kconfig option to hide the details of
>> ( BAR || !BAR) ? as Jason already explained and suggested, this will
>> make it easier for the users and developers to understand the actual
>> meaning behind this tristate weird condition.
>>
>> e.g have a new keyword:
>>      reach VXLAN
>> which will be equivalent to:
>>      depends on VXLAN && !VXLAN
>
> I'd love to see that, but I'm not sure what keyword is best. For your
> suggestion of "reach", that would probably do the job, but I'm not
> sure if this ends up being more or less confusing than what we have
> today.

Ah, perfect bikeshedding topic!

Perhaps "uses"? If the dependency is enabled it gets used as a
dependency.

Of course, this is all just talk until someone(tm) posts a patch
actually making the change. I've looked at the kconfig tool sources
before; not going to make the same mistake again.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center