linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: ebrahim@gnu.org
Cc: linux-usb@vger.kernel.org
Subject: USB: serial: pl2303: add Delock Infrared device id
Date: Sat, 9 Feb 2019 10:08:23 +0100	[thread overview]
Message-ID: <20190209090823.GA3377@kroah.com> (raw)

On Sat, Feb 09, 2019 at 12:18:40PM +0330, ebrahim@gnu.org wrote:
> From: Ebrahim Byagowi <ebrahim@gnu.org>
> 
> This makes Delock Infrared adapter to work as a USB to Serial device.
> ---
>  drivers/usb/serial/pl2303.c | 1 +
>  drivers/usb/serial/pl2303.h | 3 +++
>  2 files changed, 4 insertions(+)
> 
> diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
> index 98e7a5df0..d5ec72575 100644
> --- a/drivers/usb/serial/pl2303.c
> +++ b/drivers/usb/serial/pl2303.c
> @@ -105,6 +105,7 @@ static const struct usb_device_id id_table[] = {
>  	{ USB_DEVICE(SANWA_VENDOR_ID, SANWA_PRODUCT_ID) },
>  	{ USB_DEVICE(ADLINK_VENDOR_ID, ADLINK_ND6530_PRODUCT_ID) },
>  	{ USB_DEVICE(SMART_VENDOR_ID, SMART_PRODUCT_ID) },
> +	{ USB_DEVICE(DELOCK_VENDOR_ID, DELOCK_PRODUCT_ID) },
>  	{ }					/* Terminating entry */
>  };
>  
> diff --git a/drivers/usb/serial/pl2303.h b/drivers/usb/serial/pl2303.h
> index 4e2554d55..01936de13 100644
> --- a/drivers/usb/serial/pl2303.h
> +++ b/drivers/usb/serial/pl2303.h
> @@ -153,3 +153,6 @@
>  #define SMART_VENDOR_ID	0x0b8c
>  #define SMART_PRODUCT_ID	0x2303
>  
> +/* Delock Infrared Adapter */
> +#define DELOCK_VENDOR_ID	0x1685
> +#define DELOCK_PRODUCT_ID	0x2000
> -- 
> 2.20.1
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch does not have a Signed-off-by: line.  Please read the
  kernel file, Documentation/SubmittingPatches and resend it after
  adding that line.  Note, the line needs to be in the body of the
  email, before the patch, not at the bottom of the patch or in the
  email signature.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

             reply	other threads:[~2019-02-09  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-09  9:08 Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-11 10:17 USB: serial: pl2303: add Delock Infrared device id ebrahim
2019-02-11  8:24 Johan Hovold
2019-02-09 22:19 ebrahim
2019-02-09 15:41 Johan Hovold
2019-02-09 10:44 ebrahim
2019-02-09  9:46 Johan Hovold
2019-02-09  8:48 ebrahim

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=20190209090823.GA3377@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ebrahim@gnu.org \
    --cc=linux-usb@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 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).