From: Ping-Ke Shih <pkshih@realtek.com>
To: ZeroBeat <ZeroBeat@gmx.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "Jes.Sorensen@gmail.com" <Jes.Sorensen@gmail.com>
Subject: RE: [PATCH] wifiwifi: Realtek: rtl8xxxu Add new device ID
Date: Thu, 7 Dec 2023 00:17:53 +0000 [thread overview]
Message-ID: <4cd8742d1dc247fb9a2d315be373c9d0@realtek.com> (raw)
In-Reply-To: <5fe2c3dd-5eb8-45df-9717-87808537ff6b@gmx.de>
> -----Original Message-----
> From: ZeroBeat <ZeroBeat@gmx.de>
> Sent: Wednesday, December 6, 2023 7:48 PM
> To: linux-wireless@vger.kernel.org
> Cc: Jes.Sorensen@gmail.com
> Subject: [PATCH] wifiwifi: Realtek: rtl8xxxu Add new device ID
subject prefix should be "wifi: rtl8xxxu: ..."
>
> From: Michael Dieckmann (https://github.com/ZerBea)
> To: linux-wireless
>
> Subject: [PATCH] wifi: Realtek: rtl8xxxu Add new device ID
>
> This patch will add a new device ID.
> Patch will close: https://bugzilla.kernel.org/show_bug.cgi?id=218231
>
>
> TP-Link TL-WN8200ND(UN) v3.0
> ID 2357:0126 TP-Link 802.11n NIC
> https://www.tp-link.com/de/home-networking/adapter/tl-wn8200nd/
> Sold in Germany.
Missed your sign-of-by, and this patch looks irregular.
Please reference to https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
>
>
> --- linux/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c.orig 2023-12-06 12:38:51.929484252
> +0100
> +++ linux/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c 2023-12-06 11:54:12.524302276 +0100
The directory path is incorrect.
> @@ -7957,6 +7957,8 @@ static const struct usb_device_id dev_ta
> /* found in rtl8192eu vendor driver */
> {USB_DEVICE_AND_INTERFACE_INFO(0x2357, 0x0107, 0xff, 0xff, 0xff),
> .driver_info = (unsigned long)&rtl8192eu_fops},
> +{USB_DEVICE_AND_INTERFACE_INFO(0x2357, 0x0126, 0xff, 0xff, 0xff),
> + .driver_info = (unsigned long)&rtl8192eu_fops},
The indentation is different from other existing ones.
> {USB_DEVICE_AND_INTERFACE_INFO(0x2019, 0xab33, 0xff, 0xff, 0xff),
> .driver_info = (unsigned long)&rtl8192eu_fops},
> {USB_DEVICE_AND_INTERFACE_INFO(USB_VENDOR_ID_REALTEK, 0x818c, 0xff, 0xff, 0xff),
>
>
> Thanks for maintaining this driver.
> Best regards
> Michael Dieckmann
next prev parent reply other threads:[~2023-12-07 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 11:48 [PATCH] wifiwifi: Realtek: rtl8xxxu Add new device ID ZeroBeat
2023-12-07 0:17 ` Ping-Ke Shih [this message]
2023-12-07 11:51 ` ZeroBeat
-- strict thread matches above, loose matches on Subject: below --
2023-12-07 8:46 ZeroBeat
2023-12-07 8:52 ` Ping-Ke Shih
2023-12-07 9:02 ` ZeroBeat
2023-12-07 9:38 ` ZeroBeat
2023-12-08 0:43 ` Ping-Ke Shih
2023-12-08 6:41 ` ZeroBeat
2023-12-08 7:01 ` Ping-Ke Shih
2023-12-08 7:37 ` ZeroBeat
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=4cd8742d1dc247fb9a2d315be373c9d0@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=ZeroBeat@gmx.de \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.