All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: "John D. Blair" <johnb@candicontrols.com>
Cc: Johan Hovold <johan@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] USB: cp210x: add ID for HubZ dual ZigBee and Z-Wave dongle
Date: Thu, 4 Jun 2015 19:33:09 +0200	[thread overview]
Message-ID: <20150604173309.GB27043@localhost> (raw)
In-Reply-To: <1433436421-10051-1-git-send-email-johnb@candicontrols.com>

On Thu, Jun 04, 2015 at 09:47:01AM -0700, John D. Blair wrote:
> From: "John D. Blair" <johnb@candicontrols.com>
> 
> 
> Signed-off-by: John D. Blair <johnb@candicontrols.com>
> ---
>  drivers/usb/serial/cp210x.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c
> index 9031750e7404..47eb5c0f5345 100644
> --- a/drivers/usb/serial/cp210x.c
> +++ b/drivers/usb/serial/cp210x.c
> @@ -125,6 +125,7 @@ static const struct usb_device_id id_table[] = {
>  	{ USB_DEVICE(0x10C4, 0x8857) },	/* CEL EM357 ZigBee USB Stick */
>  	{ USB_DEVICE(0x10C4, 0x88A4) }, /* MMB Networks ZigBee USB Device */
>  	{ USB_DEVICE(0x10C4, 0x88A5) }, /* Planet Innovation Ingeni ZigBee USB Device */
> +	{ USB_DEVICE(0x10C4, 0x8A2A) }, /* HubZ dual ZigBee and Z-Wave dongle */
>  	{ USB_DEVICE(0x10C4, 0x8946) }, /* Ketra N1 Wireless Interface */
>  	{ USB_DEVICE(0x10C4, 0x8977) },	/* CEL MeshWorks DevKit Device */
>  	{ USB_DEVICE(0x10C4, 0x8998) }, /* KCF Technologies PRN */

Looks like you sent v1 again.

One more try?

Johan

  reply	other threads:[~2015-06-04 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 16:47 [PATCH 1/1] USB: cp210x: add ID for HubZ dual ZigBee and Z-Wave dongle John D. Blair
2015-06-04 17:33 ` Johan Hovold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-04 20:18 John D. Blair
2015-06-04 21:24 ` Johan Hovold
2015-06-03 18:06 John D. Blair
2015-06-04  7:19 ` 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=20150604173309.GB27043@localhost \
    --to=johan@kernel.org \
    --cc=johnb@candicontrols.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.