[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNARCr8afvs=h5-ZWVs=Bkk7PSMNvX+M_SeBSF-L99UencA@mail.gmail.com>
Date: Wed, 12 Feb 2020 01:38:16 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
ALSA Development Mailing List <alsa-devel@...a-project.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [RFC] ASoC: Use imply for SND_SOC_ALL_CODECS
On Wed, Feb 12, 2020 at 1:19 AM Mark Brown <broonie@...nel.org> wrote:
>
> On Wed, Feb 12, 2020 at 01:09:30AM +0900, Masahiro Yamada wrote:
>
> > Why does SND_SOC_ALL_CODECS exist in the first place?
> > Is this compile-test or run-test?
>
> It's for compile coverage.
>
> > If it is the former, allyesconfig / allmodconfig
> > covers all of them.
>
> No it doesn't. Those only enable user selectable options, many CODEC
> drivers don't have user selectable options as they are selected by
> machine drivers some of which either have more platform specific
> dependencies that the CODEC drivers or aren't upstream.
Maybe, can you add a prompt which is only displayed
if COMPILE_TEST is enabled?
For example,
config SND_SOC_L3
tristate "some prompt" if COMPILE_TEST
In normal use-cases, this CONFIG option is hidden
since we expect it to be selected by some machine options.
If COMPILE_TEST is enabled, we can toggle as you like.
If I run
$ git grep "if COMPILE_TEST"
I see many usages of this tip.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists