From: srbaizoki4@tuta.io
To: Linux Sound <linux-sound@vger.kernel.org>
Subject: Unresolved Alsa-UCM GitHub issue redirect
Date: Tue, 9 Jan 2024 18:22:57 +0100 (CET) [thread overview]
Message-ID: <NnjEuqu--B-9@tuta.io> (raw)
Hello,
I am adviced to send you an email if this GitHub issue is not resolved:
https://github.com/alsa-project/alsa-ucm-conf/issues/344
I still have this issue, even with latest kernel:
Linux 6.6.9-200
Fedora Silverblue 39
In fact, I have this problem since at least 2020.
Please tell me what are the next steps in resolving this case?
Regards,
fiftydinar
reply other threads:[~2024-01-09 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=NnjEuqu--B-9@tuta.io \
--to=srbaizoki4@tuta.io \
--cc=linux-sound@vger.kernel.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