Re: [PATCH] ath10k: work around uninitialized vht_pfr variable

2019-07-15 Thread Kalle Valo
Arnd Bergmann writes: > As clang points out, the vht_pfr is assigned to a struct member > without being initialized in one case: > > drivers/net/wireless/ath/ath10k/mac.c:7528:7: error: variable 'vht_pfr' is > used uninitialized whenever 'if' condition > is false

Re: [PATCH v3 20/24] wireless: Remove call to memset after dma_alloc_coherent

2019-07-15 Thread Kalle Valo
Fuqian Huang writes: > In commit 518a2f1925c3 > ("dma-mapping: zero memory returned from dma_alloc_*"), > dma_alloc_coherent has already zeroed the memory. > So memset is not needed. > > Signed-off-by: Fuqian Huang > --- > Changes in v3: > - Use actual commit rather than the merge commit in

Re: [PATCH v3 20/24] wireless: Remove call to memset after dma_alloc_coherent

2019-07-15 Thread Kalle Valo
Fuqian Huang writes: > In commit 518a2f1925c3 > ("dma-mapping: zero memory returned from dma_alloc_*"), > dma_alloc_coherent has already zeroed the memory. > So memset is not needed. > > Signed-off-by: Fuqian Huang > --- > Changes in v3: > - Use actual commit rather than the merge commit in

[PATCH AUTOSEL 5.2 012/249] ath10k: add peer id check in ath10k_peer_find_by_id

2019-07-15 Thread Sasha Levin
From: Wen Gong [ Upstream commit 49ed34b835e231aa941257394716bc689bc98d9f ] For some SDIO chip, the peer id is 65535 for MPDU with error status, then test_bit will trigger buffer overflow for peer's memory, if kasan enabled, it will report error. Reason is when station is in disconnecting

[PATCH AUTOSEL 5.2 016/249] ath10k: Fix encoding for protected management frames

2019-07-15 Thread Sasha Levin
From: Rakesh Pillai [ Upstream commit 42f1bc43e6a97b9ddbe976eba9bd05306c990c75 ] Currently the protected management frames are not appended with the MIC_LEN which results in the protected management frames being encoded incorrectly. Add the extra space at the end of the protected management

[PATCH AUTOSEL 5.2 009/249] ath10k: Fix the wrong value of enums for wmi tlv stats id

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 9280f4fc06f44d0b4dc9e831f72d97b3d7cd35d3 ] The enum value for WMI_TLV_STAT_PDEV, WMI_TLV_STAT_VDEV and WMI_TLV_STAT_PEER is wrong, due to which the vdev stats are not received from firmware in wmi_update_stats event. Fix the enum values for above stats

[PATCH AUTOSEL 4.4 01/53] ath10k: Do not send probe response template for mesh

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the

[PATCH AUTOSEL 4.19 002/158] ath10k: Do not send probe response template for mesh

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the

[PATCH AUTOSEL 4.19 005/158] ath10k: add peer id check in ath10k_peer_find_by_id

2019-07-15 Thread Sasha Levin
From: Wen Gong [ Upstream commit 49ed34b835e231aa941257394716bc689bc98d9f ] For some SDIO chip, the peer id is 65535 for MPDU with error status, then test_bit will trigger buffer overflow for peer's memory, if kasan enabled, it will report error. Reason is when station is in disconnecting

[PATCH AUTOSEL 4.19 108/158] ath10k: add missing error handling

2019-07-15 Thread Sasha Levin
From: Claire Chang [ Upstream commit 4b553f3ca4cbde67399aa3a756c37eb92145b8a1 ] In function ath10k_sdio_mbox_rx_alloc() [sdio.c], ath10k_sdio_mbox_alloc_rx_pkt() is called without handling the error cases. This will make the driver think the allocation for skb is successful and try to access

[PATCH AUTOSEL 4.4 44/53] ath10k: fix PCIE device wake up failed

2019-07-15 Thread Sasha Levin
From: Miaoqing Pan [ Upstream commit 011d4111c8c602ea829fa4917af1818eb0500a90 ] Observed PCIE device wake up failed after ~120 iterations of soft-reboot test. The error message is "ath10k_pci :01:00.0: failed to wake up device : -110" The call trace as below: ath10k_pci_probe ->

[PATCH AUTOSEL 4.19 002/158] ath10k: Do not send probe response template for mesh

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the

[PATCH AUTOSEL 4.14 002/105] ath10k: Do not send probe response template for mesh

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the

[PATCH AUTOSEL 5.1 145/219] ath10k: fix fw crash by moving chip reset after napi disabled

2019-07-15 Thread Sasha Levin
From: Miaoqing Pan [ Upstream commit 08d80e4cd27ba19f9bee9e5f788f9a9fc440a22f ] On SMP platform, when continuously running wifi up/down, the napi poll can be scheduled during chip reset, which will call ath10k_pci_has_fw_crashed() to check the fw status. But in the reset period, the value from

[PATCH AUTOSEL 5.1 146/219] ath10k: fix PCIE device wake up failed

2019-07-15 Thread Sasha Levin
From: Miaoqing Pan [ Upstream commit 011d4111c8c602ea829fa4917af1818eb0500a90 ] Observed PCIE device wake up failed after ~120 iterations of soft-reboot test. The error message is "ath10k_pci :01:00.0: failed to wake up device : -110" The call trace as below: ath10k_pci_probe ->

[PATCH AUTOSEL 5.1 144/219] ath10k: add missing error handling

2019-07-15 Thread Sasha Levin
From: Claire Chang [ Upstream commit 4b553f3ca4cbde67399aa3a756c37eb92145b8a1 ] In function ath10k_sdio_mbox_rx_alloc() [sdio.c], ath10k_sdio_mbox_alloc_rx_pkt() is called without handling the error cases. This will make the driver think the allocation for skb is successful and try to access

[PATCH AUTOSEL 4.9 01/73] ath10k: Do not send probe response template for mesh

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the

[PATCH AUTOSEL 5.2 002/249] ath10k: htt: don't use txdone_fifo with SDIO

2019-07-15 Thread Sasha Levin
From: Alagu Sankar [ Upstream commit e2a6b711282a371c5153239e0468a48254f17ca6 ] HTT High Latency (ATH10K_DEV_TYPE_HL) does not use txdone_fifo at all, we don't even initialise it by skipping ath10k_htt_tx_alloc_buf() in ath10k_htt_tx_start(). Because of this using QCA6174 SDIO

[PATCH AUTOSEL 5.2 006/249] ath10k: Do not send probe response template for mesh

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the

[PATCH AUTOSEL 5.2 003/249] ath10k: fix incorrect multicast/broadcast rate setting

2019-07-15 Thread Sasha Levin
From: Pradeep kumar Chitrapu [ Upstream commit 93ee3d108fc77e19efeac3ec5aa7d5886711bfef ] Invalid rate code is sent to firmware when multicast rate value of 0 is sent to driver indicating disabled case, causing broken mesh path. so fix that. Tested on QCA9984 with firmware 10.4-3.6.1-00827

[PATCH AUTOSEL 5.2 001/249] ath10k: Check tx_stats before use it

2019-07-15 Thread Sasha Levin
From: Yingying Tang [ Upstream commit 9e7251fa38978b85108c44743e1436d48e8d0d76 ] tx_stats will be freed and set to NULL before debugfs_sta node is removed in station disconnetion process. So if read the debugfs_sta node there may be NULL pointer error. Add check for tx_stats before use it to

[PATCH AUTOSEL 5.2 164/249] ath10k: fix fw crash by moving chip reset after napi disabled

2019-07-15 Thread Sasha Levin
From: Miaoqing Pan [ Upstream commit 08d80e4cd27ba19f9bee9e5f788f9a9fc440a22f ] On SMP platform, when continuously running wifi up/down, the napi poll can be scheduled during chip reset, which will call ath10k_pci_has_fw_crashed() to check the fw status. But in the reset period, the value from

[PATCH AUTOSEL 5.2 163/249] ath10k: add missing error handling

2019-07-15 Thread Sasha Levin
From: Claire Chang [ Upstream commit 4b553f3ca4cbde67399aa3a756c37eb92145b8a1 ] In function ath10k_sdio_mbox_rx_alloc() [sdio.c], ath10k_sdio_mbox_alloc_rx_pkt() is called without handling the error cases. This will make the driver think the allocation for skb is successful and try to access

[PATCH AUTOSEL 5.2 165/249] ath10k: fix PCIE device wake up failed

2019-07-15 Thread Sasha Levin
From: Miaoqing Pan [ Upstream commit 011d4111c8c602ea829fa4917af1818eb0500a90 ] Observed PCIE device wake up failed after ~120 iterations of soft-reboot test. The error message is "ath10k_pci :01:00.0: failed to wake up device : -110" The call trace as below: ath10k_pci_probe ->

[PATCH AUTOSEL 5.1 001/219] ath10k: Check tx_stats before use it

2019-07-15 Thread Sasha Levin
From: Yingying Tang [ Upstream commit 9e7251fa38978b85108c44743e1436d48e8d0d76 ] tx_stats will be freed and set to NULL before debugfs_sta node is removed in station disconnetion process. So if read the debugfs_sta node there may be NULL pointer error. Add check for tx_stats before use it to

[PATCH AUTOSEL 5.1 003/219] ath10k: fix incorrect multicast/broadcast rate setting

2019-07-15 Thread Sasha Levin
From: Pradeep kumar Chitrapu [ Upstream commit 93ee3d108fc77e19efeac3ec5aa7d5886711bfef ] Invalid rate code is sent to firmware when multicast rate value of 0 is sent to driver indicating disabled case, causing broken mesh path. so fix that. Tested on QCA9984 with firmware 10.4-3.6.1-00827

[PATCH AUTOSEL 5.1 002/219] ath10k: htt: don't use txdone_fifo with SDIO

2019-07-15 Thread Sasha Levin
From: Alagu Sankar [ Upstream commit e2a6b711282a371c5153239e0468a48254f17ca6 ] HTT High Latency (ATH10K_DEV_TYPE_HL) does not use txdone_fifo at all, we don't even initialise it by skipping ath10k_htt_tx_alloc_buf() in ath10k_htt_tx_start(). Because of this using QCA6174 SDIO

[PATCH AUTOSEL 4.19 131/158] ath10k: destroy sdio workqueue while remove sdio module

2019-07-15 Thread Sasha Levin
From: Wen Gong [ Upstream commit 3ed39f8e747a7aafeec07bb244f2c3a1bdca5730 ] The workqueue need to flush and destory while remove sdio module, otherwise it will have thread which is not destory after remove sdio modules. Tested with QCA6174 SDIO with firmware WLAN.RMH.4.4.1-7-QCARMSWP-1.

[PATCH AUTOSEL 5.1 002/219] ath10k: htt: don't use txdone_fifo with SDIO

2019-07-15 Thread Sasha Levin
From: Alagu Sankar [ Upstream commit e2a6b711282a371c5153239e0468a48254f17ca6 ] HTT High Latency (ATH10K_DEV_TYPE_HL) does not use txdone_fifo at all, we don't even initialise it by skipping ath10k_htt_tx_alloc_buf() in ath10k_htt_tx_start(). Because of this using QCA6174 SDIO

[PATCH AUTOSEL 5.1 001/219] ath10k: Check tx_stats before use it

2019-07-15 Thread Sasha Levin
From: Yingying Tang [ Upstream commit 9e7251fa38978b85108c44743e1436d48e8d0d76 ] tx_stats will be freed and set to NULL before debugfs_sta node is removed in station disconnetion process. So if read the debugfs_sta node there may be NULL pointer error. Add check for tx_stats before use it to

[PATCH AUTOSEL 5.1 012/219] ath10k: add peer id check in ath10k_peer_find_by_id

2019-07-15 Thread Sasha Levin
From: Wen Gong [ Upstream commit 49ed34b835e231aa941257394716bc689bc98d9f ] For some SDIO chip, the peer id is 65535 for MPDU with error status, then test_bit will trigger buffer overflow for peer's memory, if kasan enabled, it will report error. Reason is when station is in disconnecting

[PATCH AUTOSEL 5.1 009/219] ath10k: Fix the wrong value of enums for wmi tlv stats id

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 9280f4fc06f44d0b4dc9e831f72d97b3d7cd35d3 ] The enum value for WMI_TLV_STAT_PDEV, WMI_TLV_STAT_VDEV and WMI_TLV_STAT_PEER is wrong, due to which the vdev stats are not received from firmware in wmi_update_stats event. Fix the enum values for above stats

[PATCH AUTOSEL 5.1 016/219] ath10k: Fix encoding for protected management frames

2019-07-15 Thread Sasha Levin
From: Rakesh Pillai [ Upstream commit 42f1bc43e6a97b9ddbe976eba9bd05306c990c75 ] Currently the protected management frames are not appended with the MIC_LEN which results in the protected management frames being encoded incorrectly. Add the extra space at the end of the protected management

[PATCH AUTOSEL 5.1 006/219] ath10k: Do not send probe response template for mesh

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the

[PATCH AUTOSEL 5.1 003/219] ath10k: fix incorrect multicast/broadcast rate setting

2019-07-15 Thread Sasha Levin
From: Pradeep kumar Chitrapu [ Upstream commit 93ee3d108fc77e19efeac3ec5aa7d5886711bfef ] Invalid rate code is sent to firmware when multicast rate value of 0 is sent to driver indicating disabled case, causing broken mesh path. so fix that. Tested on QCA9984 with firmware 10.4-3.6.1-00827

[PATCH AUTOSEL 5.2 201/249] ath10k: Fix memory leak in qmi

2019-07-15 Thread Sasha Levin
From: Dundi Raviteja [ Upstream commit c709df58832c5f575f0255bea4b09ad477fc62ea ] Currently the memory allocated for qmi handle is not being freed during de-init which leads to memory leak. Free the allocated qmi memory in qmi deinit to avoid memory leak. Tested HW: WCN3990 Tested FW:

[PATCH AUTOSEL 5.1 009/219] ath10k: Fix the wrong value of enums for wmi tlv stats id

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 9280f4fc06f44d0b4dc9e831f72d97b3d7cd35d3 ] The enum value for WMI_TLV_STAT_PDEV, WMI_TLV_STAT_VDEV and WMI_TLV_STAT_PEER is wrong, due to which the vdev stats are not received from firmware in wmi_update_stats event. Fix the enum values for above stats

[PATCH AUTOSEL 5.1 006/219] ath10k: Do not send probe response template for mesh

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the

[PATCH AUTOSEL 5.1 016/219] ath10k: Fix encoding for protected management frames

2019-07-15 Thread Sasha Levin
From: Rakesh Pillai [ Upstream commit 42f1bc43e6a97b9ddbe976eba9bd05306c990c75 ] Currently the protected management frames are not appended with the MIC_LEN which results in the protected management frames being encoded incorrectly. Add the extra space at the end of the protected management

[PATCH AUTOSEL 5.1 012/219] ath10k: add peer id check in ath10k_peer_find_by_id

2019-07-15 Thread Sasha Levin
From: Wen Gong [ Upstream commit 49ed34b835e231aa941257394716bc689bc98d9f ] For some SDIO chip, the peer id is 65535 for MPDU with error status, then test_bit will trigger buffer overflow for peer's memory, if kasan enabled, it will report error. Reason is when station is in disconnecting

[PATCH AUTOSEL 4.9 54/73] ath10k: fix PCIE device wake up failed

2019-07-15 Thread Sasha Levin
From: Miaoqing Pan [ Upstream commit 011d4111c8c602ea829fa4917af1818eb0500a90 ] Observed PCIE device wake up failed after ~120 iterations of soft-reboot test. The error message is "ath10k_pci :01:00.0: failed to wake up device : -110" The call trace as below: ath10k_pci_probe ->

[PATCH AUTOSEL 5.2 001/249] ath10k: Check tx_stats before use it

2019-07-15 Thread Sasha Levin
From: Yingying Tang [ Upstream commit 9e7251fa38978b85108c44743e1436d48e8d0d76 ] tx_stats will be freed and set to NULL before debugfs_sta node is removed in station disconnetion process. So if read the debugfs_sta node there may be NULL pointer error. Add check for tx_stats before use it to

[PATCH AUTOSEL 5.2 006/249] ath10k: Do not send probe response template for mesh

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the

[PATCH AUTOSEL 5.2 009/249] ath10k: Fix the wrong value of enums for wmi tlv stats id

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 9280f4fc06f44d0b4dc9e831f72d97b3d7cd35d3 ] The enum value for WMI_TLV_STAT_PDEV, WMI_TLV_STAT_VDEV and WMI_TLV_STAT_PEER is wrong, due to which the vdev stats are not received from firmware in wmi_update_stats event. Fix the enum values for above stats

[PATCH AUTOSEL 5.2 012/249] ath10k: add peer id check in ath10k_peer_find_by_id

2019-07-15 Thread Sasha Levin
From: Wen Gong [ Upstream commit 49ed34b835e231aa941257394716bc689bc98d9f ] For some SDIO chip, the peer id is 65535 for MPDU with error status, then test_bit will trigger buffer overflow for peer's memory, if kasan enabled, it will report error. Reason is when station is in disconnecting

[PATCH AUTOSEL 5.2 016/249] ath10k: Fix encoding for protected management frames

2019-07-15 Thread Sasha Levin
From: Rakesh Pillai [ Upstream commit 42f1bc43e6a97b9ddbe976eba9bd05306c990c75 ] Currently the protected management frames are not appended with the MIC_LEN which results in the protected management frames being encoded incorrectly. Add the extra space at the end of the protected management

[PATCH AUTOSEL 5.2 002/249] ath10k: htt: don't use txdone_fifo with SDIO

2019-07-15 Thread Sasha Levin
From: Alagu Sankar [ Upstream commit e2a6b711282a371c5153239e0468a48254f17ca6 ] HTT High Latency (ATH10K_DEV_TYPE_HL) does not use txdone_fifo at all, we don't even initialise it by skipping ath10k_htt_tx_alloc_buf() in ath10k_htt_tx_start(). Because of this using QCA6174 SDIO

[PATCH AUTOSEL 5.2 003/249] ath10k: fix incorrect multicast/broadcast rate setting

2019-07-15 Thread Sasha Levin
From: Pradeep kumar Chitrapu [ Upstream commit 93ee3d108fc77e19efeac3ec5aa7d5886711bfef ] Invalid rate code is sent to firmware when multicast rate value of 0 is sent to driver indicating disabled case, causing broken mesh path. so fix that. Tested on QCA9984 with firmware 10.4-3.6.1-00827

[PATCH AUTOSEL 5.1 176/219] ath10k: destroy sdio workqueue while remove sdio module

2019-07-15 Thread Sasha Levin
From: Wen Gong [ Upstream commit 3ed39f8e747a7aafeec07bb244f2c3a1bdca5730 ] The workqueue need to flush and destory while remove sdio module, otherwise it will have thread which is not destory after remove sdio modules. Tested with QCA6174 SDIO with firmware WLAN.RMH.4.4.1-7-QCARMSWP-1.

[PATCH AUTOSEL 5.1 175/219] ath10k: Fix memory leak in qmi

2019-07-15 Thread Sasha Levin
From: Dundi Raviteja [ Upstream commit c709df58832c5f575f0255bea4b09ad477fc62ea ] Currently the memory allocated for qmi handle is not being freed during de-init which leads to memory leak. Free the allocated qmi memory in qmi deinit to avoid memory leak. Tested HW: WCN3990 Tested FW:

[PATCH AUTOSEL 4.19 109/158] ath10k: fix PCIE device wake up failed

2019-07-15 Thread Sasha Levin
From: Miaoqing Pan [ Upstream commit 011d4111c8c602ea829fa4917af1818eb0500a90 ] Observed PCIE device wake up failed after ~120 iterations of soft-reboot test. The error message is "ath10k_pci :01:00.0: failed to wake up device : -110" The call trace as below: ath10k_pci_probe ->

[PATCH AUTOSEL 4.14 002/105] ath10k: Do not send probe response template for mesh

2019-07-15 Thread Sasha Levin
From: Surabhi Vishnoi [ Upstream commit 97354f2c432788e3163134df6bb144f4b6289d87 ] Currently mac80211 do not support probe response template for mesh point. When WMI_SERVICE_BEACON_OFFLOAD is enabled, host driver tries to configure probe response template for mesh, but it fails because the

[PATCH AUTOSEL 4.14 076/105] ath10k: add missing error handling

2019-07-15 Thread Sasha Levin
From: Claire Chang [ Upstream commit 4b553f3ca4cbde67399aa3a756c37eb92145b8a1 ] In function ath10k_sdio_mbox_rx_alloc() [sdio.c], ath10k_sdio_mbox_alloc_rx_pkt() is called without handling the error cases. This will make the driver think the allocation for skb is successful and try to access

[PATCH AUTOSEL 4.14 091/105] ath10k: destroy sdio workqueue while remove sdio module

2019-07-15 Thread Sasha Levin
From: Wen Gong [ Upstream commit 3ed39f8e747a7aafeec07bb244f2c3a1bdca5730 ] The workqueue need to flush and destory while remove sdio module, otherwise it will have thread which is not destory after remove sdio modules. Tested with QCA6174 SDIO with firmware WLAN.RMH.4.4.1-7-QCARMSWP-1.

Re: [PATCH] ath10k: work around uninitialized vht_pfr variable

2019-07-15 Thread Kalle Valo
Arnd Bergmann wrote: > As clang points out, the vht_pfr is assigned to a struct member > without being initialized in one case: > > drivers/net/wireless/ath/ath10k/mac.c:7528:7: error: variable 'vht_pfr' is > used uninitialized whenever 'if' condition > is false

Re: [PATCH] ath10k: work around uninitialized vht_pfr variable

2019-07-15 Thread Kalle Valo
Arnd Bergmann wrote: > As clang points out, the vht_pfr is assigned to a struct member > without being initialized in one case: > > drivers/net/wireless/ath/ath10k/mac.c:7528:7: error: variable 'vht_pfr' is > used uninitialized whenever 'if' condition > is false