On Sun, Dec 01, 2013 at 12:36:52AM -0600, Larry Finger wrote: > On 11/30/2013 10:27 PM, gregkh@xxxxxxxxxxxxxxxxxxx wrote: > > > > The patch below does not apply to the 3.10-stable tree. > > If someone wants it applied there, or to any other stable or longterm > > tree, then please email the backport, including the original git commit > > id to <stable@xxxxxxxxxxxxxxx>. > > > > thanks, > > > > greg k-h > > Greg, > > The patch below backports commit 3545f3d to kernel 3.10. > > Thanks, > > Larry > > ------------------ original commit in Linus's tree ------------------ > > >From 3545f3d5f4af715c914394123ce7725a9cf0a1c4 Mon Sep 17 00:00:00 2001 > From: Larry Finger <Larry.Finger@xxxxxxxxxxxx> > Date: Tue, 5 Nov 2013 15:15:30 -0600 > Subject: [PATCH] rtlwifi: rtl8192de: Fix incorrect signal strength for > unassociated AP > > The routine that processes received frames was returning the RSSI value for the > signal strength; however, that value is available only for associated APs. As > a result, the strength was the absurd value of 10 dBm. As a result, scans > return incorrect values for the strength, which causes unwanted attempts to roam. > > Signed-off-by: Larry Finger <Larry.Finger@xxxxxxxxxxxx> > Cc: Stable <stable@xxxxxxxxxxxxxxx> [3.1+] > Signed-off-by: John W. Linville <linville@xxxxxxxxxxxxx> > > Index: linux-2.6/drivers/net/wireless/rtlwifi/rtl8192de/trx.c > =================================================================== > --- linux-2.6.orig/drivers/net/wireless/rtlwifi/rtl8192de/trx.c > +++ linux-2.6/drivers/net/wireless/rtlwifi/rtl8192de/trx.c > @@ -525,7 +525,7 @@ bool rtl92de_rx_query_desc(struct ieee80 > p_drvinfo); > } > /*rx_status->qual = stats->signal; */ > - rx_status->signal = stats->rssi + 10; > + rx_status->signal = stats->recvsignalpower + 10; > /*rx_status->noise = -stats->noise; */ > return true; > } Whitespace issues on all 3 of these patches as well, but I can edit these by hand... greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html