From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217501] Apple USB-C 3.5mm dongle cannot output 41000hz
Date: Thu, 02 Jan 2025 09:48:43 +0000 [thread overview]
Message-ID: <bug-217501-208809-IP1sPEiKoz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217501-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217501
Takashi Iwai (tiwai@suse.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Sound(ALSA) |USB
Assignee|perex@perex.cz |drivers_usb@kernel-bugs.ker
| |nel.org
--- Comment #15 from Takashi Iwai (tiwai@suse.de) ---
A good spot after long time!
As it seems like an issue in the USB core side, let's toss to USB devs.
--
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 parent reply other threads:[~2025-01-02 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-217501-208809@https.bugzilla.kernel.org/>
2025-01-02 9:48 ` bugzilla-daemon [this message]
2025-01-04 8:10 ` [Bug 217501] Apple USB-C 3.5mm dongle cannot output 41000hz 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-217501-208809-IP1sPEiKoz@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