mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Huang Wei <huangwei@kylinos.cn>
To: Johan Hovold <johan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	leStoppe <lestoppe@gmail.com>, Craig Hesling <craig@hesling.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	huangwei@kylinos.cn
Subject: Re: [PATCH v2] USB: serial: simple: narrow OWON match to avoid breaking VDS1022
Date: Mon, 16 Nov 2026 10:45:07 +0800	[thread overview]
Message-ID: <20261116024507.2633503-1-huangwei@kylinos.cn> (raw)
In-Reply-To: <20261015025456.3927808-1-huangwei@kylinos.cn>

Hi Johan,

Following up on this thread. The last open question from the November
3rd analysis is how to proceed given that the VDS1022I reports the
same interface tuple (5, 0, 0) as the HDS200 - the interface-level
narrowing doesn't reliably separate the device families.

The v2 is ready if the full-tuple approach is acceptable, but given
the new data it may need to be reverted to the original broad match
or approached differently. Could you share your preference when you
get a chance?

Thanks,
Huang Wei

  parent reply	other threads:[~2026-11-16  2:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10  9:13 [PATCH] " Huang Wei
2026-08-10 11:43 ` Greg Kroah-Hartman
2026-08-10 19:40   ` leStoppe
2026-08-11 13:17     ` Huang Wei
2026-08-11 15:18       ` Amit
2026-08-11  7:39   ` Michal Pecio
2026-08-11 13:05   ` Huang Wei
2026-08-17  8:47 ` Johan Hovold
2026-08-17  9:35   ` Huang Wei
2026-10-13 21:42     ` Amit
2026-10-15  2:54       ` Huang Wei
2026-10-29 23:46         ` craig
2026-10-30  1:28           ` Huang Wei
2026-10-30  7:44             ` craig
2026-11-03  2:23               ` Huang Wei
2026-10-15  2:54 ` [PATCH v2] " Huang Wei
2026-10-28  2:15   ` Huang Wei
2026-11-16  2:45   ` Huang Wei [this message]
2026-11-16  9:37     ` Greg Kroah-Hartman

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=20261116024507.2633503-1-huangwei@kylinos.cn \
    --to=huangwei@kylinos.cn \
    --cc=craig@hesling.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=lestoppe@gmail.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®