<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net/wireless, branch v4.6</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v4.6</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v4.6'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2016-05-06T11:27:48Z</updated>
<entry>
<title>Merge tag 'iwlwifi-for-kalle-2016-05-04' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes</title>
<updated>2016-05-06T11:27:48Z</updated>
<author>
<name>Kalle Valo</name>
<email>kvalo@codeaurora.org</email>
</author>
<published>2016-05-06T11:27:48Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=cbbba30f1ac95a04aae9c61a55aebe5e6fdf29f0'/>
<id>urn:sha1:cbbba30f1ac95a04aae9c61a55aebe5e6fdf29f0</id>
<content type='text'>
* fix P2P rates (and possibly other issues)
</content>
</entry>
<entry>
<title>iwlwifi: mvm: don't override the rate with the AMSDU len</title>
<updated>2016-05-04T17:59:55Z</updated>
<author>
<name>Emmanuel Grumbach</name>
<email>emmanuel.grumbach@intel.com</email>
</author>
<published>2016-05-03T09:08:43Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5c08b0f5026fcc13efb947c4d1f2ca3558145f68'/>
<id>urn:sha1:5c08b0f5026fcc13efb947c4d1f2ca3558145f68</id>
<content type='text'>
The TSO code creates A-MSDUs from a single large send. Each
A-MSDU is an skb and skb-&gt;len doesn't include the number of
bytes which need to be added for the headers being added
(subframe header, TCP header, IP header, SNAP, padding).

To be able to set the right value in the Tx command, we
put the number of bytes added by those headers in
driver_data in iwl_mvm_tx_tso and use this value in
iwl_mvm_set_tx_cmd.

The problem by setting this value in driver_data is that
it overrides the ieee80211_tx_info. The bug manifested
itself when we send P2P related frames in CCK since the
rate in ieee80211_tx_info is zero-ed. This of course is
a violation of the P2P specification.

To fix this, copy the original ieee80211_tx_info to the
stack and pass it to the functions which need it.
Assign the number of bytes added by the headers to the
driver_data inside the skb itself.

Fixes: a6d5e32f247c ("iwlwifi: mvm: send large SKBs to the transport")
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'iwlwifi-for-kalle-2016-04-12_2' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes</title>
<updated>2016-04-21T12:40:13Z</updated>
<author>
<name>Kalle Valo</name>
<email>kvalo@codeaurora.org</email>
</author>
<published>2016-04-21T12:40:13Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=e2841ea91611622370f66b4dfaa62599e8850d48'/>
<id>urn:sha1:e2841ea91611622370f66b4dfaa62599e8850d48</id>
<content type='text'>
* add new device IDs for 8265
* fix a NULL pointer dereference when paging firmware asserts
* remove a WARNING on gscan capabilities
* fix MODULE_FIRMWARE for 8260
</content>
</entry>
<entry>
<title>ath9k: ar5008_hw_cmn_spur_mitigate: add missing mask_m &amp; mask_p initialisation</title>
<updated>2016-04-15T18:03:54Z</updated>
<author>
<name>Oleksij Rempel</name>
<email>linux@rempel-privat.de</email>
</author>
<published>2016-04-12T17:37:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=de478a61389cacafe94dc8b035081b681b878f9d'/>
<id>urn:sha1:de478a61389cacafe94dc8b035081b681b878f9d</id>
<content type='text'>
by moving common code to ar5008_hw_cmn_spur_mitigate i forgot to move
mask_m &amp; mask_p initialisation. This coused a performance regression
on ar9281.

Fixes: f911085ffa88 ("ath9k: split ar5008_hw_spur_mitigate and reuse common code in ar9002_hw_spur_mitigate.")
Reported-by: Gustav Frederiksen &lt;lkml2017@openmailbox.org&gt;
Tested-by: Gustav Frederiksen &lt;lkml2017@openmailbox.org&gt;
Cc: &lt;stable@vger.kernel.org&gt; # 4.2+
Signed-off-by: Oleksij Rempel &lt;linux@rempel-privat.de&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
<entry>
<title>iwlwifi: mvm: fix accessing Null pointer during fw dump collection</title>
<updated>2016-04-12T08:52:39Z</updated>
<author>
<name>Matti Gottlieb</name>
<email>matti.gottlieb@intel.com</email>
</author>
<published>2016-04-10T07:53:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f742aaf36edf0390c54d0614bc4d20fd4cd3762a'/>
<id>urn:sha1:f742aaf36edf0390c54d0614bc4d20fd4cd3762a</id>
<content type='text'>
The firwmare file can come with data that is relevant for paging. This
data is availablet to the firmware upon request, but it stored in the
host's memory. During the firmware init flow, the driver configures the
firmware so that the firwmare knows where is the data.
When paging is used, the variable paging_mem_size is the number of bytes
that are available through paging. This variable is not zeror-ed if the
driver fails to configure the paging in the firmware, but the memory is
freed which is inconsistent.
This inconsistency led to a NULL pointer dereference in the code that
collects the debug data.

Fix this by zero-ing the paging_mem_size variable and NULLify the
relevant pointers, so that the code that collects the debug data will
know that the paging data is not available.

Signed-off-by: Matti Gottlieb &lt;matti.gottlieb@intel.com&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>iwlwifi: 8000: fix MODULE_FIRMWARE input</title>
<updated>2016-04-12T08:52:29Z</updated>
<author>
<name>Sara Sharon</name>
<email>sara.sharon@intel.com</email>
</author>
<published>2016-04-11T12:01:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=e1ba684f762b9a8064de2c916bb60b1694dd8a17'/>
<id>urn:sha1:e1ba684f762b9a8064de2c916bb60b1694dd8a17</id>
<content type='text'>
The firwmare name for 8000 is iwlwifi-8000C. The C is
appended based on a value read from a register. This
allows to load different firwmare versions based on
the hardware step during development. Now that the
hardware development is completed, we can hard code
the 'C' and along the way, fix the input to
MODULE_FIRMWARE.

This fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=116041

Signed-off-by: Sara Sharon &lt;sara.sharon@intel.com&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>iwlwifi: mvm: avoid to WARN about gscan capabilities</title>
<updated>2016-04-12T07:03:16Z</updated>
<author>
<name>Ayala Beker</name>
<email>ayala.beker@intel.com</email>
</author>
<published>2016-02-03T13:36:52Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=cd49727e1a2bccc4ff008dde24c2f8430dd9e368'/>
<id>urn:sha1:cd49727e1a2bccc4ff008dde24c2f8430dd9e368</id>
<content type='text'>
Gscan capabilities were updated with new capabilities supported
by the device. Update GSCAN capabilities TLV and avoid to WARN
if the firmware does not have the new capabilities.

Signed-off-by: Ayala Beker &lt;ayala.beker@intel.com&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>iwlwifi: add device IDs for the 8265 device</title>
<updated>2016-04-12T07:03:16Z</updated>
<author>
<name>Oren Givon</name>
<email>oren.givon@intel.com</email>
</author>
<published>2016-03-24T08:20:28Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d34475b964b01067ed25187c4f52d8bdf2c0e113'/>
<id>urn:sha1:d34475b964b01067ed25187c4f52d8bdf2c0e113</id>
<content type='text'>
Add new 8265 series PCI IDs.

Signed-off-by: Oren Givon &lt;oren.givon@intel.com&gt;
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'iwlwifi-for-kalle-2016-03-30' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes</title>
<updated>2016-04-02T14:59:57Z</updated>
<author>
<name>Kalle Valo</name>
<email>kvalo@codeaurora.org</email>
</author>
<published>2016-04-02T14:59:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=15da5d11040c636cddf85bd93fd4abe85f02fc9f'/>
<id>urn:sha1:15da5d11040c636cddf85bd93fd4abe85f02fc9f</id>
<content type='text'>
* lower the debug level of a benign print
* fix a memory leak
</content>
</entry>
<entry>
<title>rtlwifi: fix gcc-6 indentation warning</title>
<updated>2016-03-23T15:52:56Z</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2016-03-17T10:03:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=2acd846485549655582ee379ceb966206f91e6f8'/>
<id>urn:sha1:2acd846485549655582ee379ceb966206f91e6f8</id>
<content type='text'>
The rtl8821ae_dm_txpower_tracking_callback_thermalmeter function
contains a call to RT_TRACE() that is indented in a misleading
way, as pointed out by a gcc-6 warning:

drivers/net/wireless/realtek/rtlwifi/rtl8821ae/dm.c: In function 'rtl8821ae_dm_txpower_tracking_callback_thermalmeter':
drivers/net/wireless/realtek/rtlwifi/rtl8821ae/dm.c:2491:4: error: statement is indented as if it were guarded by...
    RT_TRACE(rtlpriv, COMP_POWER_TRACKING, DBG_LOUD,
    ^~~~~~~~
drivers/net/wireless/realtek/rtlwifi/rtl8821ae/dm.c:2488:3: note: ...this 'for' clause, but it is not
   for (p = RF90_PATH_A; p &lt; MAX_PATH_NUM_8821A; p++)
   ^~~

It is clear from the context that the call was not meant to be
part of the loop and only the indentation is wrong, so this
removes the extra tabs.

Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Acked-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Signed-off-by: Kalle Valo &lt;kvalo@codeaurora.org&gt;
</content>
</entry>
</feed>
