From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220193] PATCH 6.1 082/167 which adds support for Owon HDS200 breaks functionality of Owon VDS1022
Date: Mon, 12 Oct 2026 08:18:44 +0000 [thread overview]
Message-ID: <bug-220193-208809-Z5NTBUa2dg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220193-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220193
Wei Huang (daway320@163.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daway320@163.com
--- Comment #5 from Wei Huang (daway320@163.com) ---
Hi leStoppe,
Friendly follow-up on the request from August - no pressure at all if you've
been busy.
To recap: the patch fixing the VDS1022 regression is ready and was reviewed by
the USB serial maintainer, but he asked for a few details about the device
before it can be finalized. The one thing that would really help is the output
of:
lsusb -v -d 5345:1234
run with the VDS1022 plugged in (needs root; if it prints nothing, a plain
"lsusb -v" also works). If you can also mention which application you use to
talk to the scope (a libusb-based one?), that would settle the remaining review
question.
If you no longer have access to the device, just say so and I'll note it on the
mailing list - no problem either way.
Thanks a lot!
--
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-10-12 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 21:09 [Bug 220193] New: PATCH 6.1 082/167 which adds support for Owon HDS200 breaks functionality of Owon VDS1022 bugzilla-daemon
2026-08-10 9:47 ` [Bug 220193] " bugzilla-daemon
2026-08-10 19:35 ` bugzilla-daemon
2026-08-11 13:24 ` bugzilla-daemon
2026-08-26 2:50 ` bugzilla-daemon
2026-10-12 8:18 ` 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-220193-208809-Z5NTBUa2dg@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