From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2: sof-soundwire: Simplify cs42l45 configs
Date: Mon, 8 Dec 2025 12:41:31 +0100 (CET) [thread overview]
Message-ID: <187f3aa4bf9a2800-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/655@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #655 was opened from mstrozek:
Continued from https://github.com/alsa-project/alsa-ucm-conf/pull/644
Simplify cs42l45 configs following machine driver changes [1] which bring normal switches instead of mute switches.
[1] https://lore.kernel.org/all/20251127163426.2500633-2-ckeepax@opensource.cirrus.com/
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/655
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/655.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2025-12-08 11:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/655@alsa-project.org>]
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=187f3aa4bf9a2800-webhooks-bot@alsa-project.org \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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).