From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: bugs@lists.linux.dev, tiwai@suse.com,
alsa-devel@alsa-project.org, perex@perex.cz
Subject: Re: Asus ROG Zephyrus GX701L sound problem
Date: Sat, 27 May 2023 19:28:18 +0000 [thread overview]
Message-ID: <20230527-b216392c2-2360e52d040f@bugzilla.kernel.org> (raw)
In-Reply-To: <20230331-b216392c1-7a8e13d80aac@bugzilla.kernel.org>
mpagano writes via Kernel.org Bugzilla:
(In reply to Ivan from comment #1)
> Any news?
There at least an acknowledgement of the growing problem and a statement that it's being worked on.
https://lore.kernel.org/lkml/1991650.PYKUYFuaPT@fedora/
View: https://bugzilla.kernel.org/show_bug.cgi?id=216392#c2
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
next prev parent reply other threads:[~2023-05-27 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 17:59 Asus ROG Zephyrus GX701L sound problem Kernel.org Bugbot
2023-03-31 17:59 ` Kernel.org Bugbot
2023-05-27 19:28 ` Kernel.org Bugbot [this message]
2023-11-21 7:25 ` Kernel.org Bugbot
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=20230527-b216392c2-2360e52d040f@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bugs@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).