From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@google.com>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com, Mark Brown <broonie@kernel.org>
Subject: [PATCH 1/2] kunit: Enable ASoC in all_tests.config
Date: Wed, 12 Jul 2023 16:40:34 +0100 [thread overview]
Message-ID: <20230712-asoc-topology-kunit-enable-v1-1-b9f2da9dca23@kernel.org> (raw)
In-Reply-To: <20230712-asoc-topology-kunit-enable-v1-0-b9f2da9dca23@kernel.org>
There are KUnit tests for some of the ASoC utility functions which are
not enabled in the KUnit all_tests.config, do so.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/testing/kunit/configs/all_tests.config | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tools/testing/kunit/configs/all_tests.config b/tools/testing/kunit/configs/all_tests.config
index 0393940c706a..13d15bc693fb 100644
--- a/tools/testing/kunit/configs/all_tests.config
+++ b/tools/testing/kunit/configs/all_tests.config
@@ -35,3 +35,7 @@ CONFIG_DAMON_DBGFS=y
CONFIG_SECURITY=y
CONFIG_SECURITY_APPARMOR=y
+
+CONFIG_SOUND=y
+CONFIG_SND=y
+CONFIG_SND_SOC=y
--
2.39.2
next prev parent reply other threads:[~2023-07-12 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 15:40 [PATCH 0/2] ASoC: Improve coverage in default KUnit runs Mark Brown
2023-07-12 15:40 ` Mark Brown [this message]
2023-07-13 4:19 ` [PATCH 1/2] kunit: Enable ASoC in all_tests.config David Gow
2023-07-13 10:27 ` Mark Brown
2023-07-12 15:40 ` [PATCH 2/2] ASoC: topology: Add explicit build option Mark Brown
2023-07-13 4:19 ` David Gow
2023-07-19 13:57 ` [PATCH 0/2] ASoC: Improve coverage in default KUnit runs 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=20230712-asoc-topology-kunit-enable-v1-1-b9f2da9dca23@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=perex@perex.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.