Re: your mail
From: Johan Hovold
Date: Mon Jul 16 2018 - 06:03:23 EST
On Mon, Jul 16, 2018 at 09:46:05AM +0800, MovieSong wrote:
> From cff42ec450bdd1fb44dd80564cb622660a9a8071 Mon Sep 17 00:00:00 2001
> From: Movie Song <MovieSong@xxxxxxxxxxxxx>
> Date: Fri, 13 Jul 2018 17:46:19 +0800
> Subject: [PATCH] This add a new device for ATEN
>
> Signed-off-by: Movie Song <MovieSong@xxxxxxxxxxxxx>
First, your mail still has the legal disclaimer footer which prevents us
from using this patch.
Second, the patch is now inline, but it's unfortunately white-space
damaged (tabs replaces with spaces).
Take a look at
https://marc.info/?l=linux-usb&m=150576193231309
for an example of what the subject and commit message should look like.
Send it to yourself first and make sure it has no legal disclaimer
footers, and that you can apply it using git-am.
> ---
> drivers/usb/serial/pl2303.c | 2 ++
> drivers/usb/serial/pl2303.h | 1 +
> 2 files changed, 3 insertions(+)
>
> diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
> index 5d1a193..99f7e1f 100644
> --- a/drivers/usb/serial/pl2303.c
> +++ b/drivers/usb/serial/pl2303.c
> @@ -52,6 +52,8 @@
> .driver_info = PL2303_QUIRK_ENDPOINT_HACK },
> { USB_DEVICE(ATEN_VENDOR_ID, ATEN_PRODUCT_UC485),
> .driver_info = PL2303_QUIRK_ENDPOINT_HACK },
> + { USB_DEVICE(ATEN_VENDOR_ID, ATEN_PRODUCT_UC485),
> + .driver_info = PL2303_QUIRK_ENDPOINT_HACK },
And here you add a duplicate entry instead of the one based on the new
id you add.
> { USB_DEVICE(ATEN_VENDOR_ID, ATEN_PRODUCT_ID2) },
> { USB_DEVICE(ATEN_VENDOR_ID2, ATEN_PRODUCT_ID) },
> { USB_DEVICE(ELCOM_VENDOR_ID, ELCOM_PRODUCT_ID) },
> diff --git a/drivers/usb/serial/pl2303.h b/drivers/usb/serial/pl2303.h
> index fcd7239..26965cc 100644
> --- a/drivers/usb/serial/pl2303.h
> +++ b/drivers/usb/serial/pl2303.h
> @@ -24,6 +24,7 @@
> #define ATEN_VENDOR_ID2 0x0547
> #define ATEN_PRODUCT_ID 0x2008
> #define ATEN_PRODUCT_UC485 0x2021
> +#define ATEN_PRODUCT_UC232B 0x2022
> #define ATEN_PRODUCT_ID2 0x2118
>
> #define IODATA_VENDOR_ID 0x04bb
Thanks,
Johan