netdev - Re: ath9k: bring back direction setting in ath9k_{start

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8737lbx33a.fsf@kamboji.qca.qualcomm.com>
Date:   Wed, 07 Sep 2016 16:16:09 +0300
From:   Kalle Valo <kvalo@...eaurora.org>
To:     Giedrius Statkevi?ius <giedrius.statkevicius@...il.com>
Cc:     <ath9k-devel@....qualcomm.com>, <linux-wireless@...r.kernel.org>,
        <ath9k-devel@...ts.ath9k.org>, <netdev@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>,
        Miaoqing Pan <miaoqing@...eaurora.org>,
        <stable@...r.kernel.org>
Subject: Re: ath9k: bring back direction setting in ath9k_{start_stop}

Kalle Valo <kvalo@....qualcomm.com> writes:

> Giedrius Statkevi?ius <giedrius.statkevicius@...il.com> wrote:
>> A regression was introduced in commit id 79d4db1214a ("ath9k: cleanup
>> led_pin initial") that broken the WLAN status led on my laptop with
>> AR9287 after suspending and resuming.
>> 
>> Steps to reproduce:
>> * Suspend (laptop)
>> * Resume (laptop)
>> * Observe that the WLAN led no longer turns ON/OFF depending on the
>>   status and is always red
>> 
>> Even though for my case it only needs to be set to OUT in ath9k_start
>> but for consistency bring back the IN direction setting as well.
>> 
>> Cc: Miaoqing Pan <miaoqing@...eaurora.org>
>> Cc: Kalle Valo <kvalo@....qualcomm.com>
>> Cc: <stable@...r.kernel.org>
>> Signed-off-by: Giedrius Statkevičius <giedrius.statkevicius@...il.com>
>
> Thanks, 1 patch applied to ath-next branch of ath.git:
>
> 088a60926b66 ath9k: bring back direction setting in ath9k_{start_stop}

Oops, I was supposed to apply this to ath-current branch. Please ignore
this. Luckily I didn't push yet so I can easily fix this.

-- 
Kalle Valo