STRICTLY CONFIDENTIAL

I have important transaction for you as next of kin to claim US$18.37m Mail me on my private email: chimwia...@gmail.com so I can send you more details Thanks Mr.Chim Wai Kim MOVE TO INBOX=== DISCLAIMER: This email and any files it contains are confidential

Re: pull-request: mac80211 2016-12-16

From: Johannes Berg Date: Fri, 16 Dec 2016 13:39:56 +0100 > Since you seem to be updating net, I thought I'd send you a few fixes. > These aren't really all that important though, so if you want to let > them wait for a bit I can live with that. > > Please pull and

[PATCH v4] cfg80211: NL80211_ATTR_SOCKET_OWNER support for CMD_CONNECT

Disconnect or deauthenticate when the owning socket is closed if this flag is supplied to CMD_CONNECT or CMD_ASSOCIATE. This may be used to ensure userspace daemon doesn't leave an unmanaged connection behind. In some situations it would be possible to account for that, to some degree, in the

Re: [PATCH 3/3][RFC] nl80211/mac80211: Accept multiple RSSI thresholds for CQM

On 13 December 2016 at 11:11, Johannes Berg wrote: > >> I wasn't clear: nl80211 sets the thresholds so that "high" is higher >> than last known value and "low" is lower than last known value, also >> the distance is at least 2 x hysteresis. There's no purpose for >>

Re: [PATCH v3] cfg80211: NL80211_ATTR_SOCKET_OWNER support for CMD_CONNECT

Hi, On 13 December 2016 at 10:33, Johannes Berg wrote: > [snip] > > Please fix coding style, particularly indentation. Ok, fixed the wrapped lines. > >> +static void cfg80211_disconnect_wk(struct work_struct *work) >> +{ >> + struct cfg80211_registered_device

[PATCH] net: wireless: marvell: libertas: constify cfg80211_ops structures

cfg80211_ops structures are only passed as an argument to the function wiphy_new. This argument is of type const, so cfg80211_ops strutures having this property can be declared as const. Done using Coccinelle @r1 disable optional_qualifier @ identifier i; position p; @@ static struct cfg80211_ops

[PATCH] net: wireless: ath: wil6210: constify cfg80211_ops structures

cfg80211_ops structures are only passed as an argument to the function wiphy_new. This argument is of type const, so cfg80211_ops strutures having this property can be declared as const. Done using Coccinelle @r1 disable optional_qualifier @ identifier i; position p; @@ static struct cfg80211_ops

Re: [Patch] NFC: trf7970a:

Mark, from our consultant: It isn't important whether the flood script is successful in writing or not. The point of it is to force a segfault by making many requests. It needs to run for several hundred iterations (successful or not) in order to generate the segfault. Geoff Geoff Lansberry

[PATCH] rtlwifi: rtl8192ee: New firmware from Realtek

From: Troy Tan Recent testing by Realtek found bugs in both the driver and firmware for the RTL8192EE chips. Signed-off-by: Troy Tan Signed-off-by: Larry Finger --- WHENCE | 5 -

[PATCH] ath10k: merge extended peer info data with existing peers info

The 10.4 firmware adds extended peer information to the firmware's statistics payload. This additional info is stored as a separate data field. During review of "ath10k: add accounting for the extended peer statistics" [0] Mohammed Shafi Shajakhan commented that the extended peer statistics lists

Re: [PATCH v2 0/7] ath9k: EEPROM swapping improvements

Hi Adrian, On Wed, Dec 14, 2016 at 7:45 AM, Adrian Chadd wrote: > hi, > > On 12 December 2016 at 12:05, Martin Blumenstingl > wrote: > >> >> It seems that there are a few devices out there where the whole EEPROM >> is swab16'ed which

MAC address in wl1251 NVS data (Was: Re: wl1251 NVS calibration data format)

> On Sat, Dec 17, 2016 at 12:14:50PM +0100, Pali Rohár wrote: > > > [1] http://notaz.gp2x.de/misc/pnd/wl1251/nvs_map.txt > > In that description is something about STA mac address: > > 019 02 //length > > 01a 6d //STA_ADDR_L Register Address. (STA MAC > >

Re: wl1251 NVS calibration data format

Hi, On Sat, Dec 17, 2016 at 12:14:50PM +0100, Pali Rohár wrote: > On Saturday 17 December 2016 10:37:05 Sebastian Reichel wrote: > > On Fri, Dec 16, 2016 at 12:01:48PM +0100, Pali Rohár wrote: > > > Hi! Do you know format of wl1251 NVS calibration data file? > > > > > > I found that there is

Re: wl1251 NVS calibration data format

On Saturday 17 December 2016 10:37:05 Sebastian Reichel wrote: > Hi, > > On Fri, Dec 16, 2016 at 12:01:48PM +0100, Pali Rohár wrote: > > Hi! Do you know format of wl1251 NVS calibration data file? > > > > I found that there is tool for changing NVS file for wl1271 and > > newer chips (so not for

Re: wl1251 NVS calibration data format

Hi, On Fri, Dec 16, 2016 at 12:01:48PM +0100, Pali Rohár wrote: > Hi! Do you know format of wl1251 NVS calibration data file? > > I found that there is tool for changing NVS file for wl1271 and newer > chips (so not for wl1251!) at: https://github.com/gxk/ti-utils > > And wl1271 has in NVS