Re: [PATCH] USB: Serial: option: add a Longcheer device id

From: gregkh@xxxxxxxxxxxxxxxxxxx
Date: Tue Jun 16 2020 - 06:05:57 EST


On Tue, Jun 16, 2020 at 07:55:10AM +0000, Gao, Nian wrote:
> >From 9220e0828f70a34c968e32d34e13281a4ff54b08 Mon Sep 17 00:00:00 2001
> From: Gao Nian <nian.gao@xxxxxxxxxxx>
> Date: Tue, 16 Jun 2020 15:13:48 +0800
> Subject: [PATCH] USB: Serial: option: add a Longcheer device id
>
> Add a Longcheer device-id entry which specifically enables
> U9300C TD-LTE module.
>
> Signed-off-by: Gao Nian <nian.gao@xxxxxxxxxxx>
> ---
> drivers/usb/serial/option.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c
> index 254a8bbeea67..6fd92431d2c9 100644
> --- a/drivers/usb/serial/option.c
> +++ b/drivers/usb/serial/option.c
> @@ -394,6 +394,9 @@ static void option_instat_callback(struct urb *urb);
> /* iBall 3.5G connect wireless modem */
> #define IBALL_3_5G_CONNECT 0x9605
> +/* LONGSUNG U9300C TD-LTE wireless modem */
> +#define LONGSUNG_U9300C 0x9b3c
> +
> /* Zoom */
> #define ZOOM_PRODUCT_4597 0x9607
> @@ -1845,6 +1848,7 @@ static const struct usb_device_id option_ids[] = {
> .driver_info = RSVD(4) },
> { USB_DEVICE(LONGCHEER_VENDOR_ID, ZOOM_PRODUCT_4597) },
> { USB_DEVICE(LONGCHEER_VENDOR_ID, IBALL_3_5G_CONNECT) },
> + { USB_DEVICE(LONGCHEER_VENDOR_ID, LONGSUNG_U9300C) },
> { USB_DEVICE(HAIER_VENDOR_ID, HAIER_PRODUCT_CE100) },
> { USB_DEVICE_AND_INTERFACE_INFO(HAIER_VENDOR_ID, HAIER_PRODUCT_CE81B, 0xff, 0xff, 0xff) },
> /* Pirelli */
> --
> 2.25.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 is malformed (tabs converted to spaces, linewrapped, etc.)
and can not be applied. Please read the file,
Documentation/email-clients.txt in order to fix this.

- Your patch was attached, please place it inline so that it can be
applied directly from the email message itself.


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