All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nathaniel Ting <nathaniel.ting@silabs.com>
Cc: Johan Hovold <johan@kernel.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: serial: cp210x: Add Silicon Labs 358x VID and PID.
Date: Thu, 2 Oct 2014 15:20:37 -0700	[thread overview]
Message-ID: <20141002222037.GA31369@kroah.com> (raw)
In-Reply-To: <542DC5C9.8020301@silabs.com>

On Thu, Oct 02, 2014 at 05:38:17PM -0400, Nathaniel Ting wrote:
> From: Nathaniel Ting <nathaniel.ting@silabs.com>
> 
> Enable Silicon Labs Ember VID chips to enumerate with the cp210x usb serial
> driver. EM358x devices operating with the Ember Z-Net 5.1.2 stack may now
> connect to host PCs over a USB serial link.
> 
> Signed-off-by: Nathaniel Ting <nathaniel.ting@silabs.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 e4bb622..ce81fa8 100644
> --- a/drivers/usb/serial/cp210x.c
> +++ b/drivers/usb/serial/cp210x.c
> @@ -154,6 +154,7 @@ static const struct usb_device_id id_table[] = {
>      { USB_DEVICE(0x18EF, 0xE00F) }, /* ELV USB-I2C-Interface */
>      { USB_DEVICE(0x1ADB, 0x0001) }, /* Schweitzer Engineering C662 Cable */
>      { USB_DEVICE(0x1B1C, 0x1C00) }, /* Corsair USB Dongle */
> +        { USB_DEVICE(0x1BA4, 0x0002) }, /* Silicon Labs 358x factory default */

Your whitespace is corrupted here, making the patch impossible to apply
:(

  reply	other threads:[~2014-10-02 22:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 21:38 [PATCH] USB: serial: cp210x: Add Silicon Labs 358x VID and PID Nathaniel Ting
2014-10-02 22:20 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-03 15:06 Nathaniel Ting
2014-10-03 15:50 ` Greg KH
2014-10-03 16:01 Nathaniel Ting
2014-10-03 17:14 ` Greg KH
2014-10-22  8:13 ` 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=20141002222037.GA31369@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nathaniel.ting@silabs.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 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.