From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
johan@kernel.org, richard.leitner@skidata.com,
felipe.balbi@linux.intel.com
Subject: [v2] USB: misc: uss720: more vendor/product ID's
Date: Tue, 20 Mar 2018 12:28:03 +0100 [thread overview]
Message-ID: <20180320112803.GA21216@kroah.com> (raw)
On Tue, Mar 20, 2018 at 03:58:47AM -0700, Daniel Gimpelevich wrote:
> Reporting two more VID/PID pairs that work with this driver, having used
> an informational webpage <http://reboots.g-cipher.net/lcd/> as a buying
> guide now. The page listed additional working VID/PID pairs but did not
> include these two. None were upstreamed. Also taking this opportunity to
> sort the pairs numerically.
>
> Of the two such cables now in my possession, one is white, bearing the
> In-System Design ISD-103 label on one side, sold as an Epson CAEUL0002
> "USB to Parallel Smart Cable For Apple Macintosh Computers" (04b8:0002),
> and the other is black, bearing the In-System Design ISD-101 label on one
> side, sold as an early Belkin F5U002 (05ab:0002).
>
> Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
> ---
> drivers/usb/misc/uss720.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
For the next time, you should put the versioning of the patch below the
--- line, saying what changed in each version, so we remember what is
going on here.
thanks,
greg k-h
---
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
next reply other threads:[~2018-03-20 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 11:28 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-20 10:58 [v2] USB: misc: uss720: more vendor/product ID's 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=20180320112803.GA21216@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel@gimpelevich.san-francisco.ca.us \
--cc=felipe.balbi@linux.intel.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=richard.leitner@skidata.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;
as well as URLs for NNTP newsgroup(s).