linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Johan Hovold <johan@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] usb: serial: usb_debug: Add new USB device id
Date: Tue, 28 Nov 2017 10:01:13 +0100	[thread overview]
Message-ID: <20171128090113.GG9862@localhost> (raw)
In-Reply-To: <1511844059-17866-1-git-send-email-baolu.lu@linux.intel.com>

On Tue, Nov 28, 2017 at 12:40:59PM +0800, Lu Baolu wrote:
> USB vendor id and product id for Linux USB Debug Target is added.
> 
> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> ---
>  drivers/usb/serial/usb_debug.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/usb/serial/usb_debug.c b/drivers/usb/serial/usb_debug.c
> index ab5a2ac..47636b6 100644
> --- a/drivers/usb/serial/usb_debug.c
> +++ b/drivers/usb/serial/usb_debug.c
> @@ -32,12 +32,14 @@ static const struct usb_device_id id_table[] = {
>  
>  static const struct usb_device_id dbc_id_table[] = {
>  	{ USB_DEVICE(0x1d6b, 0x0011) },
> +	{ USB_DEVICE(0x1d6b, 0x0010) },
>  	{ },
>  };
>  
>  static const struct usb_device_id id_table_combined[] = {
>  	{ USB_DEVICE(0x0525, 0x127a) },
>  	{ USB_DEVICE(0x1d6b, 0x0011) },
> +	{ USB_DEVICE(0x1d6b, 0x0010) },
>  	{ },
>  };
>  MODULE_DEVICE_TABLE(usb, id_table_combined);

For next time, please try to keep the device-id tables sorted when
adding new entries. I fixed it up before applying with a stable tag.

Thanks,
Johan

  reply	other threads:[~2017-11-28  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28  4:40 [PATCH 1/1] usb: serial: usb_debug: Add new USB device id Lu Baolu
2017-11-28  9:01 ` Johan Hovold [this message]
2017-11-28 23:37   ` Lu Baolu

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=20171128090113.GG9862@localhost \
    --to=johan@kernel.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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).