public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Slark Xiao <slark_xiao@163.com>
Cc: Johan Hovold <johan@kernel.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Re: Re: Re: [PATCH] USB: serial: option: add support for Foxconn T99W651
Date: Mon, 2 Sep 2024 07:59:28 +0200	[thread overview]
Message-ID: <2024090237-pacemaker-natural-e0ff@gregkh> (raw)
In-Reply-To: <6c85e8f3.4bab.191b0e374ee.Coremail.slark_xiao@163.com>

On Mon, Sep 02, 2024 at 11:59:42AM +0800, Slark Xiao wrote:
> At 2024-07-05 17:39:56, "Greg KH" <gregkh@linuxfoundation.org> wrote:
> >On Fri, Jul 05, 2024 at 05:34:06PM +0800, Slark Xiao wrote:
> >> 
> >> At 2024-07-05 17:22:13, "Johan Hovold" <johan@kernel.org> wrote:
> >> >On Fri, Jul 05, 2024 at 05:11:22PM +0800, Slark Xiao wrote:
> >> >
> >> >> I have a concern about the test result of "usb-devices" in Ubuntu
> >> >> 22.04. Do you know why it wouldn't show our devices any more? 
> >> >
> >> >No, sorry, no idea. Everything seems to work here with the latest
> >> >usbutils-017.
> >> >
> >> >Is it just your devices that no longer show up or doesn't it work at
> >> >all?
> >> >
> >> A lot of devices missed in Ubuntu 22.04, especially for modem devices.
> >> Nothing would be printed for modem devices.
> >
> >What specific version of usbutils are you using?
> >
> >If you pull from the github repo, can you try the version there?
> >
> >And if that has problems, a diff of both working and not-working would
> >be great.
> >
> >thanks,
> >
> >greg k-h
> Hi Greg,
> I reproduced this issue again. And now I checked it with different usbutils
> version one by one.  Version 014 has this issue. Both 013 and 015 works well.
> Please see attached log:

So this is fine now with the latest version?  Note that 015 was released
way back in 2022 and that is even quite old, 017 is the latest release
of usbutils.

A problem in usb-devices was fixed in the 015 release, dealing with
recursion and overwriting existing variables, so odds are that is what
fixed the problem you were having.  Please just use that or newer and
all should be fine.

thanks,

greg k-h

  reply	other threads:[~2024-09-02  5:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05  8:17 [PATCH] USB: serial: option: add support for Foxconn T99W651 Slark Xiao
2024-07-05  9:06 ` Johan Hovold
2024-07-05  9:11   ` Slark Xiao
2024-07-05  9:22     ` Johan Hovold
2024-07-05  9:34       ` Slark Xiao
2024-07-05  9:39         ` Greg KH
2024-09-02  3:59           ` Slark Xiao
2024-09-02  5:59             ` Greg KH [this message]
2024-09-02  6:46               ` Re:Re: " Slark Xiao
2024-09-02  6:52                 ` Greg KH

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=2024090237-pacemaker-natural-e0ff@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=slark_xiao@163.com \
    /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