From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/3] ASoC: amd: acp: Dependency cleanup
Date: Tue, 26 Oct 2021 17:11:20 +0200 [thread overview]
Message-ID: <cover.1635260849.git.geert+renesas@glider.be> (raw)
Hi all,
This patch series cleans up the dependencies of the various
configuration symbols related to AMD Audio-Coprocessor support.
Feel free to squash into a single patch if you prefer that.
Thanks!
Geert Uytterhoeven (3):
ASoC: amd: acp: Wrap AMD Audio ACP components in
SND_SOC_AMD_ACP_COMMON
ASoC: amd: acp: SND_SOC_AMD_{LEGACY_MACH,SOF_MACH} should depend on
X86 && PCI && I2C
ASoC: amd: acp: SND_SOC_AMD_ACP_COMMON should depend on X86 && PCI
sound/soc/amd/acp/Kconfig | 7 +++++++
1 file changed, 7 insertions(+)
--
2.25.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2021-10-26 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 15:11 Geert Uytterhoeven [this message]
2021-10-26 15:11 ` [PATCH 1/3] ASoC: amd: acp: Wrap AMD Audio ACP components in SND_SOC_AMD_ACP_COMMON Geert Uytterhoeven
2021-10-26 15:11 ` [PATCH 2/3] ASoC: amd: acp: SND_SOC_AMD_{LEGACY_MACH,SOF_MACH} should depend on X86 && PCI && I2C Geert Uytterhoeven
2021-10-26 15:11 ` [PATCH 3/3] ASoC: amd: acp: SND_SOC_AMD_ACP_COMMON should depend on X86 && PCI Geert Uytterhoeven
2021-10-26 19:06 ` [PATCH 0/3] ASoC: amd: acp: Dependency cleanup 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=cover.1635260849.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=AjitKumar.Pandey@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox