[PATCH 1/2] wireless: move prism54 out to staging

prism54 is deprecated in favor of the p54pci device driver. Although only *one soul* had reported issues with it long ago Linux most Linux distributions these days just disable the device driver given the conflicts with the PCI IDs of p54pci and the *very* unlikely situation of folks really need

[PATCH 2/2] MAINTAINERS: update email address for mcgrof for few straggling drivers

This will ensure I get emails on my work and personal email address. Signed-off-by: Luis R. Rodriguez --- MAINTAINERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 97cf436e6750..49ae596584e7 100644 --- a/MAINTAINERS

[PATCH 0/2] wireless: move prism54 to staging

Kalle, Greg, This moves the prism54 diver to staging. The reason for this are stated on the driver's own commit log. Let me know what tree you'd prefer this to go through. Luis R. Rodriguez (2): wireless: move prism54 out to staging MAINTAINERS: update email address for mcgrof for few

[PATCH v4 03/10] wil6210: support FW RSSI reporting

From: Dedy Lansky New FW supports reporting RSSI signal in dBm. Report RSSI to kernel in case FW has this capability. Signed-off-by: Dedy Lansky Signed-off-by: Maya Erez ---

[PATCH v4 08/10] wil6210: store FW RF calibration result

From: Dedy Lansky Store initial FW RF calibration result in driver. Set this calibration result back to FW after each FW reset in order to avoid future calibration procedures. Signed-off-by: Dedy Lansky Signed-off-by: Maya Erez

[PATCH v4 10/10] wil6210: make debugfs compilation optional

From: Gidon Studinski Since debugfs is a kernel configuration option, enable the driver to compile without debugfs. Signed-off-by: Gidon Studinski Signed-off-by: Maya Erez ---

[PATCH v4 06/10] wil6210: notify wiphy on wowlan support

Set wowlan to indicate that 11ad device can wake-up on any trigger and disconnect. Signed-off-by: Maya Erez --- drivers/net/wireless/ath/wil6210/cfg80211.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/net/wireless/ath/wil6210/cfg80211.c

[PATCH v4 07/10] wil6210: fix interface-up check

From: Hamad Kadmany While wil_open is executed, any call to netif_running would return a success. In case there are failures within wil_open, should not treat the device as if it is already opened in relevant functions (like FW recovery and runtime suspend check).

[PATCH v4 05/10] wil6210: add statistics for suspend time

Add statistics for total, min and max suspend time, that calculates the time the 11ad device was in suspend. Those statistics will help to estimate the power impact of d3hot feature. Signed-off-by: Maya Erez --- drivers/net/wireless/ath/wil6210/debugfs.c | 17

[PATCH v4 04/10] wil6210: check no_fw_recovery in resume failure recovery

Reset 11ad device on resume failure only if no_fw_recovery is not set. Signed-off-by: Maya Erez --- drivers/net/wireless/ath/wil6210/pm.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/net/wireless/ath/wil6210/pm.c

[PATCH v4 01/10] wil6210: protect against invalid length of tx management frame

From: Hamad Kadmany Validate buffer length has the minimum needed size when sending management frame to protect against possible buffer overrun. Signed-off-by: Hamad Kadmany Signed-off-by: Lior David

[PATCH v4 02/10] wil6210: allow configuring scan timers

From: Hamad Kadmany Allow setting scan timeout and scan dwell time through module parameters. Signed-off-by: Hamad Kadmany Signed-off-by: Maya Erez --- drivers/net/wireless/ath/wil6210/cfg80211.c | 17

Re: [PATCH V5 1/2] firmware: add more flexible request_firmware_async function

On Thu, Aug 03, 2017 at 05:55:18AM +, Coelho, Luciano wrote: > On Thu, 2017-08-03 at 08:23 +0300, Kalle Valo wrote: > > "Luis R. Rodriguez" writes: > > > > > > +int request_firmware_nowait(struct module *module, bool uevent, > > > > + const char

Re: [PATCH 2/2] qlcnic: add const to bin_attribute structure

From: Bhumika Goyal Date: Wed, 2 Aug 2017 23:27:14 +0530 > Add const to bin_attribute structure as it is only passed to the > functions sysfs_{remove/create}_bin_file. The corresponding > arguments are of type const, so declare the structure to be const. > > Signed-off-by:

[PATCH v2] rt2x00: Fix MMIC Countermeasures.

From: Michael Skeffington Set RX_FLAG_DECRYPTED in case of MMIC failure so that ieee80211_rx_h_decrypt() doesnt drop the frame before getting to ieee80211_rx_h_michael_mic_verify(). Signed-off-by: Michael Skeffington ---

[PATCH] ath9k: make ath_ps_ops structures as const

ath_ps_ops structures are only stored as a reference in the ps_ops field of a ath_common structure. This field is of type const, so make the structures as const. Signed-off-by: Bhumika Goyal --- drivers/net/wireless/ath/ath9k/htc_drv_init.c | 2 +-

[PATCH v3] iwlwifi: Demote messages about fw flags size to info

These messages are not reporting a real error, just the fact that the firmware knows about more flags than the driver. Currently these messages are presented to the user during boot if there is no bootsplash covering the console, even when booting the kernel with "quiet". Demoting it to the warn

RE: [PATCH v2] iwlwifi: Demote messages about fw flags size to info

From: João Paulo Rechi Vita > Sent: 03 August 2017 15:30 > These messages are not reporting a real error, just the fact that the > firmware knows about more flags then the driver. than > > Currently these messages are presented to the user during boot if there >

Re: [PATCH 3/8] rsi: add support for legacy power save

On Wed, Aug 2, 2017 at 3:20 PM, Kalle Valo wrote: > Amitkumar Karwar writes: > >> From: Karun Eagalapati >> >> This patch adds support for legacy power save. Necessary >> configuration frames are downloaded to firmware when power

[v2 8/8] rsi: RTS threshold configuration

From: Karun Eagalapati Provision is added for configuring RTS threshold by sending vap dynamic update frame to firmware. Signed-off-by: Karun Eagalapati Signed-off-by: Amitkumar Karwar ---

[v2 7/8] rsi: buffer available interrupt handling

From: Karun Eagalapati BUFFER_AVAILABLE interrupt is sent by firmware to indicate change in buffer status. We should check buffer status while handling this interrupt. Currently buffer status is checked only while dequeueing packets. This patch fixes a data traffic stuck

[v2 6/8] rsi: buffer full check optimization

From: Karun Eagalapati We get buffer full event from firmware whenever Tx queue is full Host should stop writing packets after this and resume after buffer free event. Buffer status checking is optimized for once in 4 times if BUFF_FULL condition is not set, otherwise once

[v2 5/8] rsi: rename sdio_read_buffer_status_register

From: Karun Eagalapati rsi_sdio_check_buffer_status would be the appropriate name for this function as we are checking hardware buffers availability status. Signed-off-by: Karun Eagalapati Signed-off-by: Amitkumar Karwar

[v2 4/8] rsi: add support for U-APSD power save

From: Karun Eagalapati This patch adds support for U-APSD power save. Configuration frame is downloaded to firmware with default settings and support is advertised to mac80211 Signed-off-by: Karun Eagalapati Signed-off-by: Amitkumar Karwar

[v2 3/8] rsi: add support for legacy power save

From: Karun Eagalapati This patch adds support for legacy power save. Necessary configuration frames are downloaded to firmware when power save is enabled/disabled Signed-off-by: Karun Eagalapati Signed-off-by: Amitkumar Karwar

[v2 2/8] rsi: update set_antenna command frame

From: Pavani Muthyala TX command frame set_antenna is modified to use common descriptor structure. Also it's subframe type is set. Signed-off-by: Pavani Muthyala Signed-off-by: Amitkumar Karwar

[v2 1/8] rsi: add support for rf-kill functionality

From: Pavani Muthyala This patch implements rfkill_poll handler. Also, necessary changes are done in interface up and down handler to support rfkill functionality. Signed-off-by: Pavani Muthyala Signed-off-by: Amitkumar

[v2 0/8] rsi driver enhancements

From: Amitkumar Karwar This patch series brings in few enhancements in rsi driver like rfkill support, U-APSD and Legacy power save support, antenna and RTS threshold configuration, improvements in reading SDIO buffer status. Changes in v2: 1/8: Pavani's name

[PATCH v2] iwlwifi: Demote messages about fw flags size to info

These messages are not reporting a real error, just the fact that the firmware knows about more flags then the driver. Currently these messages are presented to the user during boot if there is no bootsplash covering the console, even when booting the kernel with "quiet". Demoting it to the warn

[PATCH] rsi: fix uninitialized descriptor pointer issue

From: Prameela Rani Garnepudi This patch fixes the uninitialized descriptor pointer issue in function rsi_send_internal_mgmt_frame(). Descriptor should point to start of the skb data. Reported-by: Dan Carpenter Fixes: 9a629fafe7d8 ("rsi:

Re: [PATCH v3 9/9] wil6210: make debugfs compilation optional

On 03-08-17 15:25, Maya Erez wrote: > From: Gidon Studinski > > Since debugfs is a kernel configuration option, enable the driver to > compile without debugfs. > > Signed-off-by: Gidon Studinski > Signed-off-by: Maya Erez

[PATCH v3 8/9] wil6210: store FW RF calibration result

From: Dedy Lansky Store initial FW RF calibration result in driver. Set this calibration result back to FW after each FW reset in order to avoid future calibration procedures. Signed-off-by: Dedy Lansky Signed-off-by: Maya Erez

[PATCH v3 9/9] wil6210: make debugfs compilation optional

From: Gidon Studinski Since debugfs is a kernel configuration option, enable the driver to compile without debugfs. Signed-off-by: Gidon Studinski Signed-off-by: Maya Erez ---

[PATCH v3 7/9] wil6210: fix interface-up check

From: Hamad Kadmany While wil_open is executed, any call to netif_running would return a success. In case there are failures within wil_open, should not treat the device as if it is already opened in relevant functions (like FW recovery and runtime suspend check).

[PATCH v3 2/9] wil6210: allow configuring scan timers

From: Hamad Kadmany Allow setting scan timeout and scan dwell time through module parameters. Signed-off-by: Hamad Kadmany Signed-off-by: Maya Erez --- drivers/net/wireless/ath/wil6210/cfg80211.c | 17

[PATCH v3 1/9] wil6210: protect against invalid length of tx management frame

From: Hamad Kadmany Validate buffer length has the minimum needed size when sending management frame to protect against possible buffer overrun. Signed-off-by: Hamad Kadmany Signed-off-by: Lior David

[PATCH v3 6/9] wil6210: notify wiphy on wowlan support

Set wowlan to indicate that 11ad device can wake-up on any trigger and disconnect. Signed-off-by: Maya Erez --- drivers/net/wireless/ath/wil6210/cfg80211.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/net/wireless/ath/wil6210/cfg80211.c

[PATCH v3 0/9] wil6210 patches

Changes from v2: - Remove debugfs.c compilation if CONFIG_DEBUG_FS is not defined Changes from v1: - Removal of runtime PM patch, pending a fix to system suspend flow Dedy Lansky (2): wil6210: support FW RSSI reporting wil6210: store FW RF calibration result Gidon Studinski (1): wil6210:

[PATCH v3 3/9] wil6210: support FW RSSI reporting

From: Dedy Lansky New FW supports reporting RSSI signal in dBm. Report RSSI to kernel in case FW has this capability. Signed-off-by: Dedy Lansky Signed-off-by: Maya Erez ---

[PATCH v3 5/9] wil6210: add statistics for suspend time

Add statistics for total, min and max suspend time, that calculates the time the 11ad device was in suspend. Those statistics will help to estimate the power impact of d3hot feature. Signed-off-by: Maya Erez --- drivers/net/wireless/ath/wil6210/debugfs.c | 17

[PATCH v3 4/9] wil6210: check no_fw_recovery in resume failure recovery

Reset 11ad device on resume failure only if no_fw_recovery is not set. Signed-off-by: Maya Erez --- drivers/net/wireless/ath/wil6210/pm.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/net/wireless/ath/wil6210/pm.c

Re: [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock

On Thu, 3 Aug 2017, Jiri Kosina wrote: > > I see the workqueue allocation you mentioned. I'll try to move this > > allocation out of the mutex and see how it goes. > > I have been briefly looking into this as well -- it'll basically have to > be moved out of the trans_pcie->mutex context, but

Re: wcn36xx: check dma_mapping_error()

Rob Clark wrote: > Fixes splat: > > wcn36xx a204000.wcnss:smd-edge:wcnss:wifi: DMA-API: device driver failed to > check map error[device address=0xb45ba000] [size=3872 bytes] [mapped > as single] > [ cut here ] > WARNING: CPU: 0 PID:

Re: ath9k: Add Dell Wireless 1802 with wowlan capability

Rosen Penev wrote: > Add the Dell Wireless 1802 card as an AR9462 in the ath9k pci list. > Note that the wowlan feature is supported and has been tested > successfully. > > Signed-off by: Rosen Penev > Signed-off-by: Kalle Valo

Re: ath9k: fix debugfs file permission

Christoph Fritz wrote: > This patch fixes a trivial debugfs file permission issue. Debugfs > file ack_to has no write function, so S_IWUSR gets purged. > > Signed-off-by: Christoph Fritz > Signed-off-by: Kalle Valo

Re: [049/102] ath10k: explicitly request exclusive reset control

Philipp Zabel wrote: > Commit a53e35db70d1 ("reset: Ensure drivers are explicit when requesting > reset lines") started to transition the reset control request API calls > to explicitly state whether the driver needs exclusive or shared reset > control behavior. Convert

Re: [PATCHv2, 1/3] ath10k: extend wmi service map to accommodate new services

mpubb...@qti.qualcomm.com wrote: > Though there is room to accommodate 512 services in wmi service > ready event, target uses only first 4-bits of each 32-bit word for > advertising wmi services thereby limiting max wmi services to 64. > > TDLS implementation for 10.4 firmwares introduces new

Re: ath10k: sdio: fix compile warning

Erik Stromdahl wrote: > As suggested by Arnd Bergmann, replace > "while (time_before_...) {}" > with > "do {} while (time_before_...)" > > This fixes the following warnings detected by gcc 4.1.2: > > drivers/net/wireless/ath/ath10k/sdio.c: In function >

Re: [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock

On Thu, 3 Aug 2017, Coelho, Luciano wrote: > Okay, so as I understand it the problem has been there for a long time, > but the splat is only coming up now because of Thomas' patch that adds > the lockdep map[1], right? Yeah, sorry, forgot to mention that pre-49dfe2a67797 kernels wouldn't

Re: [v3,1/2] ath10k: various usb related definitions

Kalle Valo wrote: > Definitions for USB based chipsets > > Signed-off-by: Erik Stromdahl > Signed-off-by: Kalle Valo 2 patches applied to ath-next branch of ath.git, thanks. b00435e6cda6 ath10k: various usb related

Re: [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock

On Thu, 2017-08-03 at 13:02 +0300, Kalle Valo wrote: > "Coelho, Luciano" writes: > > > On Thu, 2017-08-03 at 11:10 +0200, Jiri Kosina wrote: > > > On Mon, 31 Jul 2017, Jiri Kosina wrote: > > > > > > > Hi, > > > > > > > > booting current Linus' tree, I'm seeing lockdep

Re: ath10k: set a-mpdu reference number in ath10k (receiver)

Matthias Frei wrote: > Set the a-mpdu reference number in ath10k to make it accessible in the > receivers radiotap header. Implemented as in ath9k. The reference number is > needed for troubleshooting and research at the receivers site (e.g. to > identify > mpdu's that were

Re: [PATCH v5] rtlwifi: Replace hardcode value with macro

On Thu, Aug 3, 2017 at 3:48 PM, Kalle Valo wrote: > Larry Finger writes: > >> On 08/02/2017 07:29 AM, Souptick Joarder wrote: >>> In _rtl_init_mac80211(), hardcoded value for hw->max_listen_interval >>> and hw->max_rate_tries are replaced by macro

RE: [PATCH] mwifiex: add module parameter to disable 40MHZ support in 2.4G band

Hi Arend/Kalle, > -Original Message- > From: Kalle Valo [mailto:kv...@codeaurora.org] > Sent: 2017年8月3日 18:00 > To: Arend van Spriel > Cc: Xinming Hu; Linux Wireless; Brian Norris; Dmitry Torokhov; > raja...@google.com; Zhiyuan Yang; Tim Song; Cathy Luo; Ganapathi Bhat; > Xinming Hu >

Re: [v5] rtlwifi: Replace hardcode value with macro

Souptick Joarder wrote: > In _rtl_init_mac80211(), hardcoded value for hw->max_listen_interval > and hw->max_rate_tries are replaced by macro and removed the comment. > > Signed-off-by: Souptick Joarder > Acked-by: Larry Finger

Re: [PATCH v5] rtlwifi: Replace hardcode value with macro

Larry Finger writes: > On 08/02/2017 07:29 AM, Souptick Joarder wrote: >> In _rtl_init_mac80211(), hardcoded value for hw->max_listen_interval >> and hw->max_rate_tries are replaced by macro and removed the comment. >> >> Signed-off-by: Souptick Joarder

Re: [v2,1/2] mwifiex: make addba request command clean

Xinming Hu wrote: > From: Xinming Hu > > uninitilized variable, such as .add_req_result might be magic stack > value. Initialize the structure to make it clean. > > Signed-off-by: Xinming Hu > Signed-off-by: Cathy Luo

Re: [10/11] net: qtnfmac: constify pci_device_id.

Arvind Yadav wrote: > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav >

Re: qtfnmac: Tidy up DMA mask setting

Robin Murphy wrote: > As the only caller of dma_supported() outside of DMA API internals, the > qtfnmac driver stands out and invites scrutiny. Thankfully, it's not > being used for evil, but it is entirely redundant, since it open-codes a > check that the DMA mask setting

Re: [net] hostap: Fix outdated comment about dev->destructor

Stefano Brivio wrote: > After commit cf124db566e6 ("net: Fix inconsistent teardown and > release of private netdev state."), setting > 'dev->needs_free_netdev' ensures device data is released, and > 'dev->destructor' is not used anymore. > > Fixes: cf124db566e6 ("net: Fix

Re: [01/11] rtlwifi: rtl8192de: constify pci_device_id.

Arvind Yadav wrote: > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > File size before: >text data bss dec

Re: [PATCH v2 3/3] brcmfmac: fix wrong num_different_channels when mchan feature enabled

Wright Feng writes: > brcmfmac: fix wrong num_different_channels when mchan feature enabled Here also the title is duplicated, but I'll fix that. > When the device/firmware supports multi-channel, it can have P2P > connection and regular connection with AP

Re: [PATCH v2 1/3] brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/OPEN security mode

Wright Feng writes: > brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/OPEN security mode > > When setting wpa_auth to WPA_AUTH_NONE(1) in AP mode with WEP security, > firmware will set privacy bit and add WPA OUI in VENDOR IE in beacon and > probe response. The

Re: [linuxwifi] x86/thermal: AB-BA dependency between mvm->mutex and tz->lock

"Coelho, Luciano" writes: > On Thu, 2017-08-03 at 11:10 +0200, Jiri Kosina wrote: >> On Mon, 31 Jul 2017, Jiri Kosina wrote: >> >> > Hi, >> > >> > booting current Linus' tree, I'm seeing lockdep splat (see the end of this >> > mail). >> > >> > Apparently, there is

Re: qtnfmac: Tidy up DMA mask setting

Robin Murphy wrote: > As the only caller of dma_supported() outside of DMA API internals, the > qtfnmac driver stands out and invites scrutiny. Thankfully, it's not > being used for evil, but it is entirely redundant, since it open-codes a > check that the DMA mask setting

Re: [v2,01/12] qtnfmac: updates for regulatory support

Sergey Matyukevich wrote: > On startup driver obtains regulatory rules from firmware and > enables them during wiphy registration. Later on regulatory > domain change can be requested by host. In this case firmware > is notified about the upcoming changes. If

Re: [PATCH] mwifiex: add module parameter to disable 40MHZ support in 2.4G band

Arend van Spriel writes: > On 03-08-17 11:26, Kalle Valo wrote: >> Xinming Hu writes: >> >>> From: Xinming Hu >>> >>> This patch provide a new module parameter disable_2g4_40m, with >>> which driver will not report 40M

Re: [PATCH v2 09/12] qtnfmac: implement scan timeout

Sergey Matyukevich writes: > Userspace tools may hang on scan in the case when scan completion event > is not returned by firmware. This patch implements the scan timeout > to avoid such situation. > > Signed-off-by: Igor Mitsyanko

Re: [PATCH] mwifiex: add module parameter to disable 40MHZ support in 2.4G band

On 03-08-17 11:26, Kalle Valo wrote: > Xinming Hu writes: > >> From: Xinming Hu >> >> This patch provide a new module parameter disable_2g4_40m, with >> which driver will not report 40M capability for 2.4GHZ to cfg80211. >> >> Signed-off-by: Xinming Hu

Re: [v2] rtlwifi: Fix fallback firmware loading

Sven Joachim wrote: > Commit f70e4df2b384 ("rtlwifi: Add code to read new versions of > firmware") added code to load an old firmware file if the new one is > not available. Unfortunately that code is never reached because > request_firmware_nowait() does not wait for the

Re: [v2] mwifiex: correct IE parse during association

Xinming Hu wrote: > From: Xinming Hu > > It is observed that some IEs get missed during association. > This patch correct the old IE parse code. sme->ie will be > store as wpa ie, wps ie, wapi ie and gen ie accordingly. > > Signed-off-by: Xinming Hu

[PATCH v2 2/3] brcmfmac: Add support for CYW4373 SDIO/USB chipset

From: Chi-Hsien Lin Add support for CYW4373 SDIO/USB chipset. CYW4373 is a 1x1 dual-band 11ac chipset with 20/40/80Mhz channel support. It's a WiFi/BT combo device. Signed-off-by: Chi-Hsien Lin --- v2: add new chip(4737) info in commit

[PATCH v2 3/3] brcmfmac: fix wrong num_different_channels when mchan feature enabled

brcmfmac: fix wrong num_different_channels when mchan feature enabled When the device/firmware supports multi-channel, it can have P2P connection and regular connection with AP simultaneous. In this case, the num_different_channels in wiphy info was not correct when firmware supports

Re: [BUG] rtlwifi: rtl_pci_probe: Fix fail path of _rtl_pci_find_adapter

Malcolm Priestley wrote: > _rtl_pci_find_adapter fail path will jump to label fail3 for > unsupported adapter types. > > However, on course for fail3 there will be call rtl_deinit_core > before rtl_init_core. > > For the inclusion of checking pci_iounmap this fail can be

Re: [PATCH] mwifiex: add module parameter to disable 40MHZ support in 2.4G band

Xinming Hu writes: > From: Xinming Hu > > This patch provide a new module parameter disable_2g4_40m, with > which driver will not report 40M capability for 2.4GHZ to cfg80211. > > Signed-off-by: Xinming Hu > Signed-off-by: Cathy Luo

Re: [PATCH 1/2] mwifiex: Do not change bss_num in change_virtual_intf

Xinming Hu writes: > From: Xinming Hu > > Commit "mwifiex: Do not change bss_type in change_virtual_intf" > Keep original bss_type unchanged. bss_num should keep the same > style, in this way. Unique tuple (bss_type, bss_num) will be > able to locate

Re: pull-request: iwlwifi-next 2017-08-01

Luca Coelho writes: > Hi Kalle, > > Here's my first pull-request intended for v4.14.  It contain generic > development work, with improvements, bug fixes and > cleanup all around.  More details in the tag description. > > As I mentioned earlier today, I left Emmanuel's "iwlwifi:

[PATCH 1/2] mwifiex: Do not change bss_num in change_virtual_intf

From: Xinming Hu Commit "mwifiex: Do not change bss_type in change_virtual_intf" Keep original bss_type unchanged. bss_num should keep the same style, in this way. Unique tuple (bss_type, bss_num) will be able to locate the right priv structure. Signed-off-by: Xinming Hu

[PATCH 2/2] mwifiex: wrapper wps ie in pass through tlv

From: Xinming Hu This patch wrapper wps ie in pass through tlv, so that firmware could parse correctly. Signed-off-by: Xinming Hu Signed-off-by: Cathy Luo Signed-off-by: Ganapathi Bhat ---

Re: [PATCH] rt2x00: Fix MMIC countermeasures.

On Wed, Aug 02, 2017 at 10:36:52AM -0400, Michael Skeffington wrote: > I traced through this code during MMIC failure and > ieee80211_rx_h_decrypt() drops the frame before getting to > ieee80211_rx_h_michael_mic_verify(). Johannes suggested this change > to me in response to a previous thread and

[PATCH] mwifiex: add module parameter to disable 40MHZ support in 2.4G band

From: Xinming Hu This patch provide a new module parameter disable_2g4_40m, with which driver will not report 40M capability for 2.4GHZ to cfg80211. Signed-off-by: Xinming Hu Signed-off-by: Cathy Luo Signed-off-by: Ganapathi Bhat

Re: pull-request: iwlwifi 2017-08-02

Luca Coelho writes: > Hi Kalle, > > Here is my second batch of fixes for 4.13. More details in the tag > description. > > I have sent this out before and kbuildbot didn't find any issues. > Please let me know if there are any issues. > > Cheers, > Luca. > > > The following