From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220331] FTDI serial IO - unknown device type: 0x8312
Date: Fri, 11 Jul 2025 06:00:18 +0000 [thread overview]
Message-ID: <bug-220331-208809-Xtgl3Dm4f8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220331-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220331
Artem S. Tashkinov (aros@gmx.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WILL_NOT_FIX
--- Comment #1 from Artem S. Tashkinov (aros@gmx.com) ---
1. This is an ancient kernel
2. Feature requests are not supported here
--
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-07-11 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 9:11 [Bug 220331] New: FTDI serial IO - unknown device type: 0x8312 bugzilla-daemon
2025-07-11 6:00 ` bugzilla-daemon [this message]
2025-07-21 14:58 ` [Bug 220331] " bugzilla-daemon
2025-07-21 15:37 ` Greg KH
2025-07-21 15:37 ` bugzilla-daemon
2025-08-27 8:37 ` [Bug 220331] New: " Johan Hovold
2025-08-27 8:37 ` [Bug 220331] " 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-220331-208809-Xtgl3Dm4f8@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 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.