From: Kalle Valo
Date: Tue, 20 Jan 2015 11:03:33 +0200
> more fixes for 3.19, I hope these are still appropriate. Please let me
> know if there are any issues.
Pulled, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.
This allows mac80211 to configure BIP-GMAC-128 and BIP-GMAC-256 to the
driver and also use software-implementation within mac80211 when the
driver does not support this with hardware accelaration.
Signed-off-by: Jouni Malinen
---
include/net/mac80211.h | 5 +++
net/mac80211/Makefile |
This allows mac80211 to configure BIP-CMAC-256 to the driver and also
use software-implementation within mac80211 when the driver does not
support this with hardware accelaration.
Signed-off-by: Jouni Malinen
---
include/linux/ieee80211.h | 9 +
net/mac80211/aes_cmac.c| 34
This allows mac80211 to configure CCMP-256 to the driver and also use
software-implementation within mac80211 when the driver does not support
this with hardware accelaration.
Signed-off-by: Jouni Malinen
---
net/mac80211/aes_ccm.c | 21 -
net/mac80211/aes_ccm.h | 10
This makes cfg80211 aware of the GCMP, GCMP-256, CCMP-256, BIP-GMAC-128,
BIP-GMAC-256, and BIP-CMAC-256 cipher suites. These new cipher suites
were defined in IEEE Std 802.11ac-2013.
Signed-off-by: Jouni Malinen
---
include/linux/ieee80211.h | 18 ++
net/wireless/util.c | 4
This cipher can be used only as a group management frame cipher and as
such, there is no point in validating that it is not used with non-zero
key-index. Instead, verify that it is not used as a pairwise cipher
regardless of the key index.
Signed-off-by: Jouni Malinen
---
net/wireless/util.c | 7
This allows mac80211 to configure GCMP and GCMP-256 to the driver and
also use software-implementation within mac80211 when the driver does
not support this with hardware accelaration.
Signed-off-by: Jouni Malinen
---
include/net/mac80211.h | 15 ++-
net/mac80211/Kconfig | 1 +
net/
Extracting values from it is still unsupported, but at least we'll
display some meaningful error now.
Signed-off-by: Rafał Miłecki
---
drivers/bcma/sprom.c | 3 ++-
include/linux/ssb/ssb_regs.h | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/bcma/sprom.c b/dr
Signed-off-by: Rafał Miłecki
---
drivers/bcma/main.c | 20 +---
1 file changed, 9 insertions(+), 11 deletions(-)
diff --git a/drivers/bcma/main.c b/drivers/bcma/main.c
index c3c5e0a..73b2ee3 100644
--- a/drivers/bcma/main.c
+++ b/drivers/bcma/main.c
@@ -368,12 +368,19 @@ static v
On 01/24/2015 05:55 AM, Taehee Yoo wrote:
After rtl8192cu download firmware routine, set fw_ready flag.
Signed-off-by: Taehee Yoo
---
drivers/net/wireless/rtlwifi/rtl8192cu/hw.c | 3 +++
1 file changed, 3 insertions(+)
Acked-by: Larry Finger
Thanks,
Larry
diff --git a/drivers/net/wir
Michal Kazior writes:
> This should fix a very rare occurrence of the following deadlock:
>
> [] ath10k_wmi_tx_beacons_nowait+0x1e/0x50 [ath10k_core]
> [] ath10k_wmi_op_ep_tx_credits+0x16/0x40 [ath10k_core]
> [] ath10k_htc_send+0x285/0x3d0 [ath10k_core]
> [] ath10k_wmi_cmd_send_nowait+0x8
printk and friends can now formap bitmaps using '%*pb[l]'. cpumask
and nodemask also provide cpumask_pr_args() and nodemask_pr_args()
respectively which can be used to generate the two printf arguments
necessary to format the specified cpu/nodemask.
This patch is dependent on the following two pa
On Sat, Jan 24, 2015 at 2:16 PM, Kalle Valo wrote:
> Sedat Dilek writes:
>
>> On Sat, Jan 24, 2015 at 12:34 PM, Hong Xu wrote:
>>> ath9k and ath9k_htc use the variable name "led_blink" to indicate
>>> whether the module parameter "blink" is on. This name is easy to
>>> conflict with other variab
Sedat Dilek writes:
> On Sat, Jan 24, 2015 at 12:34 PM, Hong Xu wrote:
>> ath9k and ath9k_htc use the variable name "led_blink" to indicate
>> whether the module parameter "blink" is on. This name is easy to
>> conflict with other variables, and has caused a compiler error found
>> by kbuild tes
After rtl8192cu download firmware routine, set fw_ready flag.
Signed-off-by: Taehee Yoo
---
drivers/net/wireless/rtlwifi/rtl8192cu/hw.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/wireless/rtlwifi/rtl8192cu/hw.c
b/drivers/net/wireless/rtlwifi/rtl8192cu/hw.c
index 5513217.
On Sat, Jan 24, 2015 at 12:34 PM, Hong Xu wrote:
> ath9k and ath9k_htc use the variable name "led_blink" to indicate
> whether the module parameter "blink" is on. This name is easy to
> conflict with other variables, and has caused a compiler error found
> by kbuild test bot. The compiler error is
ath9k and ath9k_htc use the variable name "led_blink" to indicate
whether the module parameter "blink" is on. This name is easy to
conflict with other variables, and has caused a compiler error found
by kbuild test bot. The compiler error is as following:
drivers/net/wireless/ath/ath9k/ath9k_htc.o
On Sat, Jan 24, 2015 at 12:20 PM, Hong Xu wrote:
> ath9k and ath9k_htc use the variable name "led_blink" to indicate
> whether the module parameter "blink" is on. This name is easy to
> conflict with other variables, and has caused a compiler error found
> by kbuild. The compiler error is as follo
On 01/24/15 00:29, Jörg Krause wrote:
Hi Arend,
On Fr, 2015-01-23 at 15:21 +0100, Arend van Spriel wrote:
On 01/23/15 13:31, Jörg Krause wrote:
Hi all,
I'm running an wireless device with Linux kernel 3.18.3 and the brcmfmac
driver. When connection the device to my network, I see from time to
On Sat, Jan 24, 2015 at 12:20 PM, Hong Xu wrote:
> ath9k and ath9k_htc use the variable name "led_blink" to indicate
> whether the module parameter "blink" is on. This name is easy to
> conflict with other variables, and has caused a compiler error found
> by kbuild. The compiler error is as follo
On Sat, Jan 24, 2015 at 12:10 PM, Hong Xu wrote:
>
> Sedat Dilek writes:
>
>> On Sat, Jan 24, 2015 at 11:23 AM, Kalle Valo wrote:
>>> Hong Xu writes:
>>>
ath9k and ath9k_htc use the variable name "led_blink" to indicate
whether the module parameter "blink" is on. This name is easy to
ath9k and ath9k_htc use the variable name "led_blink" to indicate
whether the module parameter "blink" is on. This name is easy to
conflict with other variables, and has caused a compiler error found
by kbuild. The compiler error is as following:
drivers/net/wireless/ath/ath9k/ath9k_htc.o:(.data+0
Sedat Dilek writes:
> On Sat, Jan 24, 2015 at 11:23 AM, Kalle Valo wrote:
>> Hong Xu writes:
>>
>>> ath9k and ath9k_htc use the variable name "led_blink" to indicate
>>> whether the module parameter "blink" is on. This name is easy to
>>> conflict with other variables, thus they are renamed.
>
[...]
> Working with tig I have to check the tipps of Peter Hutterer in his
> blog for my local ~/.tigrc again.
> This got lost when changing to Ubuntu/precise.
>
For tigrc... [2] has [1] included.
[3] and [4] as a reference to tig ("...is an ncurses-based text-mode
interface for git.).
- Sedat
On Sat, Jan 24, 2015 at 11:39 AM, Kalle Valo wrote:
> (I'll drop ath9k-devel as someone from there seems to be spamming with
> vacation responses)
>
> Sedat Dilek writes:
>
>> 2nd, use the Fixes tag [2] in this case with a reference to the
>> culprit commit [1].
>>
>> Fixes: 3a939a671225 ("ath9k_
On Sat, Jan 24, 2015 at 11:38 AM, Oleksij Rempel wrote:
> Am 24.01.2015 um 11:33 schrieb Sedat Dilek:
>> On Sat, Jan 24, 2015 at 11:23 AM, Kalle Valo wrote:
>>> Hong Xu writes:
>>>
ath9k and ath9k_htc use the variable name "led_blink" to indicate
whether the module parameter "blink" is
(I'll drop ath9k-devel as someone from there seems to be spamming with
vacation responses)
Sedat Dilek writes:
> 2nd, use the Fixes tag [2] in this case with a reference to the
> culprit commit [1].
>
> Fixes: 3a939a671225 ("ath9k_htc: Add a module parameter to disable blink")
Good point. I jus
Am 24.01.2015 um 11:33 schrieb Sedat Dilek:
> On Sat, Jan 24, 2015 at 11:23 AM, Kalle Valo wrote:
>> Hong Xu writes:
>>
>>> ath9k and ath9k_htc use the variable name "led_blink" to indicate
>>> whether the module parameter "blink" is on. This name is easy to
>>> conflict with other variables, thu
On Sat, Jan 24, 2015 at 11:23 AM, Kalle Valo wrote:
> Hong Xu writes:
>
>> ath9k and ath9k_htc use the variable name "led_blink" to indicate
>> whether the module parameter "blink" is on. This name is easy to
>> conflict with other variables, thus they are renamed.
>
> Please state clearly that t
ath9k and ath9k_htc use the variable name "led_blink" to indicate
whether the module parameter "blink" is on. This name is easy to
conflict with other variables, and has caused a compiler error found
by kbuild. The compiler error is as following:
drivers/net/wireless/ath/ath9k/ath9k_htc.o:(.data+0
Hong Xu writes:
> ath9k and ath9k_htc use the variable name "led_blink" to indicate
> whether the module parameter "blink" is on. This name is easy to
> conflict with other variables, thus they are renamed.
Please state clearly that this fixes a compiler error found by kbuild.
Also it's very muc
ath9k and ath9k_htc use the variable name "led_blink" to indicate
whether the module parameter "blink" is on. This name is easy to
conflict with other variables, thus they are renamed.
Signed-off-by: Hong Xu
---
drivers/net/wireless/ath/ath9k/ath9k.h| 2 +-
drivers/net/wireless/ath/ath9k
Hong Xu writes:
> Add an option "blink" to enable or disable the LED blink. The default
> value is set to 1 so that existing users would not experience any
> unexpected changes.
Just noticed v2 is applied. Please ignore this patch. I will send a fix
patch later.
Hong
--
To unsubscribe from thi
Hong Xu writes:
> Add an option "blink" to enable or disable the LED blink. The default
> value is set to 1 so that existing users would not experience any
> unexpected changes.
>
> Signed-off-by: Hong Xu
> ---
> drivers/net/wireless/ath/ath9k/htc.h | 3 +++
> drivers/net/wireless/ath/
Add an option "blink" to enable or disable the LED blink. The default
value is set to 1 so that existing users would not experience any
unexpected changes.
Signed-off-by: Hong Xu
---
drivers/net/wireless/ath/ath9k/htc.h | 3 +++
drivers/net/wireless/ath/ath9k/htc_drv_gpio.c | 4
dr
From: Luciano Coelho
If suspend starts while ieee80211_scan_completed() is running, between
the point where SCAN_COMPLETED is set and the work is queued,
ieee80211_scan_cancel() will not catch the work and we may finish
suspending before the work is actually executed, leaving the scan
running whi
36 matches
Mail list logo
