From: Johan Hovold <johan@kernel.org>
To: Preston Fick <pffick@gmail.com>
Cc: johan@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: serial: cp210x: Correcting IDs for production CEL MeshConnect USB Stick
Date: Tue, 23 Dec 2014 12:24:18 +0100 [thread overview]
Message-ID: <20141223112418.GJ30375@localhost> (raw)
In-Reply-To: <1419226419-19440-1-git-send-email-pffick@gmail.com>
On Sun, Dec 21, 2014 at 11:33:39PM -0600, Preston Fick wrote:
Please add a proper commit message here describing why this is needed.
Are there any devices with the original PID or was that just a typo?
> Signed-off-by: Preston Fick <pffick@gmail.com>
> ---
> drivers/usb/serial/cp210x.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c
> index 6c4eb3c..fb8d3fa 100644
> --- a/drivers/usb/serial/cp210x.c
> +++ b/drivers/usb/serial/cp210x.c
> @@ -120,7 +120,7 @@ static const struct usb_device_id id_table[] = {
> { USB_DEVICE(0x10C4, 0x85F8) }, /* Virtenio Preon32 */
> { USB_DEVICE(0x10C4, 0x8664) }, /* AC-Services CAN-IF */
> { USB_DEVICE(0x10C4, 0x8665) }, /* AC-Services OBD-IF */
> - { USB_DEVICE(0x10C4, 0x8875) }, /* CEL MeshConnect USB Stick */
> + { USB_DEVICE(0x10C4, 0x8857) }, /* CEL MeshConnect USB Stick */
> { USB_DEVICE(0x10C4, 0x88A4) }, /* MMB Networks ZigBee USB Device */
> { USB_DEVICE(0x10C4, 0x88A5) }, /* Planet Innovation Ingeni ZigBee USB Device */
> { USB_DEVICE(0x10C4, 0x8946) }, /* Ketra N1 Wireless Interface */
Thanks,
Johan
next prev parent reply other threads:[~2014-12-23 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 5:33 [PATCH] USB: serial: cp210x: Correcting IDs for production CEL MeshConnect USB Stick Preston Fick
2014-12-23 11:24 ` Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-27 7:32 Preston Fick
2015-01-02 14:02 ` Johan Hovold
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=20141223112418.GJ30375@localhost \
--to=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pffick@gmail.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