linux-kernel - Re: [PATCH v2] mux: remove the Kconfig question for the subsystem

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] [day] [month] [year] [list]

Message-ID: <CAHk-=wieKH8mGJzDNUKuPTeXB19+9cyDa5zyKOaRasjZuZLxDA@mail.gmail.com>
Date:   Wed, 7 Dec 2022 11:23:09 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Arnd Bergmann <arnd@...db.de>, Peter Rosin <peda@...ntia.se>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] mux: remove the Kconfig question for the subsystem

On Wed, Dec 7, 2022 at 11:15 AM Randy Dunlap <rdunlap@...radead.org> wrote:
>
> Oops. One more thing:
> Your statement leads me to conclude that since nothing selects those 3 mux drivers,
> they don't need to be in the kernel tree at all.
>
> Done. (I hope.)

What?

Randy, do you even *read* what you write? Or, perhaps even more
importantly, what *other* people write?

It's not that those individual MUX drivers need to be selected to be
asked about.

But they won't be asked about UNLESS SOMEBODY WANTS A MULTIPLEXER.

What is your problem here?

Basically, you will only see those questions if you have a driver (or
subsystem) that does

        select MULTIPLEXER

to let the Kconfig know that "yes, I'm actually interested".

If there is no use for those mux drivers, the "depends on MULTIPLEXER"
means that those STUPID AND POINTLESS questions won't be asked.

What's so hard to understand about this?

               Linus