netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Stable <stable@vger.kernel.org>
Cc: Marek Vasut <marex@denx.de>, Anders Larsen <al@alarsen.net>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Stable request 9374e7d2 "rtlwifi: rtl8192cu: Add new device ID"
Date: Tue, 28 Apr 2015 10:23:28 -0500	[thread overview]
Message-ID: <553FA5F0.1070402@lwfinger.net> (raw)
In-Reply-To: <201504281633.17160.marex@denx.de>

Please note that there are two commits just added to the mainline repo that 
should be propagated to all stable kernels. Both are addition of new USB IDs for 
an old driver, thus they will cause to side effects. Unfortunately, the Cc to 
stable was missed in the first of these, thus the need for this message. The 
second was Cc for stable, but I include it here for completeness.

The two commits in question are

commit 9374e7d2fdcad3c36dafc8d3effd554bc702c4b6
Author: Marek Vasut <marex@denx.de>
Date:   Thu Mar 26 02:16:06 2015 +0100

     rtlwifi: rtl8192cu: Add new device ID

     Add new ID for ASUS N10 WiFi dongle.

commit 2f92b314f4daff2117847ac5343c54d3d041bf78
Author: Larry Finger <Larry.Finger@lwfinger.net>
Date:   Mon Mar 23 18:14:10 2015 -0500

     rtlwifi: rtl8192cu: Add new USB ID

     USB ID 2001:330d is used for a D-Link DWA-131.


Thanks,

Larry

  reply	other threads:[~2015-04-28 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201504271819.57895.marex@denx.de>
2015-04-28 13:56 ` Stable request 9374e7d2 "rtlwifi: rtl8192cu: Add new device ID" Anders Larsen
2015-04-28 14:10   ` Marek Vasut
2015-04-28 14:22     ` Anders Larsen
2015-04-28 14:33       ` Marek Vasut
2015-04-28 15:23         ` Larry Finger [this message]
     [not found]           ` <553FA5F0.1070402-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2015-05-04  9:19             ` Luis Henriques

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=553FA5F0.1070402@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=al@alarsen.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=netdev@vger.kernel.org \
    --cc=stable@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).