public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Subbaraya Sundeep <sbhatta@marvell.com>
To: Lucas Sanchez Sagrado <lucsansag@gmail.com>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<linux-usb@vger.kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] net: usb: r8152: Add device ID for TP-Link UE200
Date: Mon, 9 Jun 2025 15:55:49 +0000	[thread overview]
Message-ID: <aEcEBUBIbLUM3dHn@64799e4f873a> (raw)
In-Reply-To: <20250609145536.26648-1-lucsansag@gmail.com>

On 2025-06-09 at 14:55:36, Lucas Sanchez Sagrado (lucsansag@gmail.com) wrote:
> The TP-Link UE200 is a RTL8152B based USB 2.0 Fast Ethernet adapter. This 
> patch adds its device ID. It has been tested on Ubuntu 22.04.5.
> 
> Signed-off-by: Lucas Sanchez Sagrado <lucsansag@gmail.com>

Reviewed-by: Subbaraya Sundeep <sbhatta@marvell.com>

Thanks,
Sundeep

> ---
>  drivers/net/usb/r8152.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
> index d6589b24c68d..44cba7acfe7d 100644
> --- a/drivers/net/usb/r8152.c
> +++ b/drivers/net/usb/r8152.c
> @@ -10054,6 +10054,7 @@ static const struct usb_device_id rtl8152_table[] = {
>  	{ USB_DEVICE(VENDOR_ID_LINKSYS, 0x0041) },
>  	{ USB_DEVICE(VENDOR_ID_NVIDIA,  0x09ff) },
>  	{ USB_DEVICE(VENDOR_ID_TPLINK,  0x0601) },
> +	{ USB_DEVICE(VENDOR_ID_TPLINK,  0x0602) },
>  	{ USB_DEVICE(VENDOR_ID_DLINK,   0xb301) },
>  	{ USB_DEVICE(VENDOR_ID_DELL,    0xb097) },
>  	{ USB_DEVICE(VENDOR_ID_ASUS,    0x1976) },
> 
> base-commit: 2c7e4a2663a1ab5a740c59c31991579b6b865a26
> -- 
> 2.34.1
> 

  reply	other threads:[~2025-06-09 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 14:55 [PATCH net-next] net: usb: r8152: Add device ID for TP-Link UE200 Lucas Sanchez Sagrado
2025-06-09 15:55 ` Subbaraya Sundeep [this message]
2025-06-10 21:50 ` patchwork-bot+netdevbpf

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=aEcEBUBIbLUM3dHn@64799e4f873a \
    --to=sbhatta@marvell.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lucsansag@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox