Re: [PATCH v8 3/7] mux: add help text for MULTIPLEXER config option
From: Josua Mayer
Date: Mon Feb 09 2026 - 05:13:00 EST
On 09/02/2026 10:06, Geert Uytterhoeven wrote:
> Hi Josua,
>
> On Sun, 8 Feb 2026 at 16:16, Josua Mayer <josua@xxxxxxxxxxxxx> wrote:
>> On 03/02/2026 15:01, Josua Mayer wrote:
>>> Add prompt and help text for CONFIG_MULTIPLEXER to allow enabling this
>>> option thorugh the kernel configuration without explicit "select" driver
>>> dependencies.
>>>
>>> Select it by default when COMPILE_TEST is set for better coverage.
>>>
>>> Signed-off-by: Josua Mayer <josua@xxxxxxxxxxxxx>
>>> ---
>>> drivers/mux/Kconfig | 8 +++++++-
>>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/mux/Kconfig b/drivers/mux/Kconfig
>>> index c68132e38138..e31c46820bdf 100644
>>> --- a/drivers/mux/Kconfig
>>> +++ b/drivers/mux/Kconfig
>>> @@ -4,7 +4,13 @@
>>> #
>>>
>>> config MULTIPLEXER
>>> - tristate
>>> + tristate "Generic Multiplexer Support" if COMPILE_TEST
>> This didn't do what I thought it would.
>> It was my intention to allow enabling this through menuconfig / .config.
>>
>> With the syntax above menuconfig shows:
>>
>> │ Symbol: MULTIPLEXER [=n]
>> │ Type : tristate
>> │ Defined at drivers/mux/Kconfig:6
>> │ Prompt: Generic Multiplexer Support
>> │ Visible if: COMPILE_TEST [=n]
>>
>> This means it cannot be selected.
> Looks like you haven't enabled COMPILE_TEST first?
Correct.
But CONFIG_MULTIPLEXER should be visible always,
not just when COMPILE_TEST is set.
>
>> Instead I (think I) should use
>> default m if COMPILE_TEST
> No, merely enabling COMPILE_TEST must not enable additional
> functionality.
>
>> Since my patch-set broke x86_64 allmodconfig and failed merge into
>> linux-next,
>> this presents an opportunity to change the above as well with v9.
> Ulf has already applied this series to mmc/next.
What would be the process to fix the build error for x86_64 allmodconfig
now?
>
> Gr{oetje,eeting}s,
>
> Geert
>