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

[Linus Torvalds <torvalds@linux-foundation.org>]

On Wed, Dec 7, 2022 at 11:03 AM Randy Dunlap <rdunlap@infradead.org> wrote:
> On 12/7/22 10:57, Arnd Bergmann wrote:
> >
> > They cannot, that is the entire point of hiding the subsystem
> > when it is not used.
>
> OK, if you say so. That doesn't make any sense to me, but whatever,
> I'll drop it.

The config phase of the kernel is one of the more annoying parts (the
rest is pretty much "make" and "make install"), and we should strive
to make it as simple and obvious as possible.

One big thing for that is to *not* ask questions that make no sense.

We already hide a number of them, either by disallowing them ("this
driver only makes sense on this architecture" kinds of things) or by
always forcing them on  ("if you're building for a PC, you're getting
the keyboard driver whether you want it or not").

And in many cases, we don't have questions at all, but enable code
based on automatic selection (ie "you wanted ACPI support, so we'll
enable CRC32 support because the ACPI code needs it").

I don't understand *why* you'd ever want more nonsensical questions?

Why would you ever want to ask a human "do you want this code that is
never used"?

That, to me, is actively a horrible thing to do. It only makes the
Kconfig worse. Don't do it.

         Linus