From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 222050] Periodic ~1s click/tick on JMTek USBFH11 (0c76:1720) USB audio playback under Linux, not present on Windows with same hardware
Date: Wed, 23 Sep 2026 18:36:15 +0000 [thread overview]
Message-ID: <bug-222050-208809-Gtt8OYPzmT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222050-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=222050
Artem S. Tashkinov (aros@gmx.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|USB |Sound(ALSA)
Assignee|drivers_usb@kernel-bugs.ker |perex@perex.cz
|nel.org |
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-09-23 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 14:53 [Bug 222050] New: Periodic ~1s click/tick on JMTek USBFH11 (0c76:1720) USB audio playback under Linux, not present on Windows with same hardware bugzilla-daemon
2026-09-23 18:36 ` bugzilla-daemon [this message]
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-222050-208809-Gtt8OYPzmT@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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