From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220246] Dell Latitude 5400: Mic Mute key stopped to work in v6.15
Date: Wed, 18 Jun 2025 21:46:51 +0000 [thread overview]
Message-ID: <bug-220246-215701-Qe4j6MrDMp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220246-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220246
--- Comment #14 from Armin Wolf (W_Armin@gmx.de) ---
It seems that the WMI event used by the dell-wmi driver is not marked as
expensive, but still requires us to call the enable/disable methods. Since we
only call those methods on devices marked as expensive the WMI event never gets
enabled.
Does the WMI event work under Windows?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-06-18 21:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 16:58 [Bug 220246] New: Dell Latitude 5400: Mic Mute key stopped to work in v6.15 bugzilla-daemon
2025-06-18 17:07 ` [Bug 220246] " bugzilla-daemon
2025-06-18 17:31 ` bugzilla-daemon
2025-06-18 17:58 ` bugzilla-daemon
2025-06-18 18:05 ` bugzilla-daemon
2025-06-18 18:42 ` bugzilla-daemon
2025-06-18 19:32 ` bugzilla-daemon
2025-06-18 19:42 ` bugzilla-daemon
2025-06-18 20:25 ` bugzilla-daemon
2025-06-18 20:46 ` bugzilla-daemon
2025-06-18 21:18 ` bugzilla-daemon
2025-06-18 21:30 ` bugzilla-daemon
2025-06-18 21:36 ` bugzilla-daemon
2025-06-18 21:37 ` bugzilla-daemon
2025-06-18 21:43 ` bugzilla-daemon
2025-06-18 21:46 ` bugzilla-daemon [this message]
2025-06-18 22:04 ` bugzilla-daemon
2025-06-19 0:17 ` bugzilla-daemon
2025-06-19 0:52 ` bugzilla-daemon
2025-06-19 19:51 ` bugzilla-daemon
2025-06-19 21:39 ` bugzilla-daemon
2025-06-19 22:10 ` bugzilla-daemon
2025-06-24 15:07 ` bugzilla-daemon
2025-06-26 17:04 ` bugzilla-daemon
2025-07-06 3:06 ` bugzilla-daemon
2025-07-06 3:07 ` bugzilla-daemon
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=bug-220246-215701-Qe4j6MrDMp@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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 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.