From: Mark Brown <broonie@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [alsa-devel] [PATCH] [RFC] ASoC: Use imply for SND_SOC_ALL_CODECS
Date: Tue, 11 Feb 2020 16:19:05 +0000 [thread overview]
Message-ID: <20200211161905.GM4543@sirena.org.uk> (raw)
In-Reply-To: <CAK7LNAQGcw1jbb=fWd_CbWv5hQrkqG_QFCw3uY4LXroONGM6BA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 519 bytes --]
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.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2020-02-11 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 9:13 [alsa-devel] [PATCH] [RFC] ASoC: Use imply for SND_SOC_ALL_CODECS Geert Uytterhoeven
2020-02-10 14:03 ` Mark Brown
2020-02-11 15:49 ` [alsa-devel] Applied "ASoC: Use imply for SND_SOC_ALL_CODECS" to the asoc tree Mark Brown
2020-02-11 16:09 ` [alsa-devel] [PATCH] [RFC] ASoC: Use imply for SND_SOC_ALL_CODECS Masahiro Yamada
2020-02-11 16:19 ` Mark Brown [this message]
2020-02-11 16:38 ` Masahiro Yamada
2020-02-11 16:45 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200211161905.GM4543@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=geert@linux-m68k.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).