linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
To: Greg KH <greg@kroah.com>
Cc: linux-usb@vger.kernel.org, Rab <reboots@g-cipher.net>
Subject: USB: misc: uss720: more vendor/product ID's
Date: Tue, 20 Mar 2018 02:23:54 -0700	[thread overview]
Message-ID: <1521537834.16361.21.camel@chimera> (raw)

On Tue, 2018-03-20 at 10:21 +0100, Greg KH wrote:
> On Tue, Mar 20, 2018 at 02:13:48AM -0700, Daniel Gimpelevich wrote:
> > On Tue, 2018-03-20 at 10:08 +0100, Greg KH wrote:
> > > Put the device "type" or "name" as a comment, that makes more sense
> > > and
> > > follows what almost all other drivers do.
> > 
> > I strongly considered this, but I ultimately decided against it in
> > consideration of the limited space for comments on the right, the lack
> > of such device identification extant in this driver, and the presence of
> > most or all of the listed devices in the usb.ids file.
> 
> There is no usb.ids file anymore :)

The "update-usbids" command still downloads
http://www.linux-usb.org/usb.ids for me.
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2018-03-20  9:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  9:23 Daniel Gimpelevich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-20  9:37 USB: misc: uss720: more vendor/product ID's Greg KH
2018-03-20  9:21 Greg KH
2018-03-20  9:13 Daniel Gimpelevich
2018-03-20  9:08 Greg KH
2018-03-20  9:03 Daniel Gimpelevich
2018-03-20  8:36 Greg KH
2018-03-20  8:35 Greg Kroah-Hartman
2018-03-14 22:20 Daniel Gimpelevich

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=1521537834.16361.21.camel@chimera \
    --to=daniel@gimpelevich.san-francisco.ca.us \
    --cc=greg@kroah.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=reboots@g-cipher.net \
    /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;
as well as URLs for NNTP newsgroup(s).