netdev - Re: [PATCH] staging: r8188eu: Add new device ID for DLink GO-USB-N150

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <547755BF.2080207@lwfinger.net>
Date:	Thu, 27 Nov 2014 10:47:59 -0600
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	netdev@...r.kernel.org, devel@...verdev.osuosl.org
Subject: Re: [PATCH] staging: r8188eu: Add new device ID for DLink GO-USB-N150

On 11/27/2014 10:28 AM, Greg KH wrote:
> On Thu, Nov 27, 2014 at 10:10:21AM -0600, Larry Finger wrote:
>> The DLink GO-USB-N150 with revision B1 uses this driver.
>>
>> Signed-off-by: Larry Finger <Larry.Finger@...inger.net>
>> ---
>>   drivers/staging/rtl8188eu/os_dep/usb_intf.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/staging/rtl8188eu/os_dep/usb_intf.c b/drivers/staging/rtl8188eu/os_dep/usb_intf.c
>> index 65a257f..d3cbcc4 100644
>> --- a/drivers/staging/rtl8188eu/os_dep/usb_intf.c
>> +++ b/drivers/staging/rtl8188eu/os_dep/usb_intf.c
>> @@ -47,6 +47,7 @@ static struct usb_device_id rtw_usb_id_tbl[] = {
>>   	{USB_DEVICE(0x07b8, 0x8179)}, /* Abocom - Abocom */
>>   	{USB_DEVICE(0x2001, 0x330F)}, /* DLink DWA-125 REV D1 */
>>   	{USB_DEVICE(0x2001, 0x3310)}, /* Dlink DWA-123 REV D1 */
>> +	{USB_DEVICE(0x2001, 0x3311)}, /* DLink GO-USB-N150 REV B1 */
>>   	{USB_DEVICE(0x0df6, 0x0076)}, /* Sitecom N150 v2 */
>>   	{}	/* Terminating entry */
>>   };
>> --
>> 2.1.2
>
> Should this also go to stable kernels?

Yes, it should. Sorry for missing that Cc.

Larry


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html