From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Sebastian Gottschall <s.gottschall@dd-wrt.com>,
svp <s.pooheer@gmail.com>
Subject: Re: QCA988x and kernel 4.13
Date: Wed, 4 Oct 2017 08:13:43 -0700 [thread overview]
Message-ID: <78f5383d-0187-628e-cf56-de6234fdb9b0@candelatech.com> (raw)
In-Reply-To: <87d163xpoe.fsf@kamboji.qca.qualcomm.com>
On 10/04/2017 01:50 AM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> writes:
>
>> On 10/01/2017 07:06 AM, Sebastian Gottschall wrote:
>>> you have to update to the latest mac80211 code. there is a well
>>> known bug in mac80211 which causes a deadlock with ath10k
>>
>> Do you have a pointer to the patch that fixes this? I'd like to check if it has
>> made it into 4.13 stable yet...
>
> I think it's this one:
>
> mac80211: fix deadlock in driver-managed RX BA session start
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bde59c475e0883e4c4294bcd9b9c7e08ae18c828
>
> Adding linux-wireless so that someone can correct me in case I'm wrong.
That did seem to fix my problems...
Thanks,
ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-10-04 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 8:39 QCA988x and kernel 4.13 svp
2017-10-01 14:06 ` Sebastian Gottschall
2017-10-02 17:24 ` Ben Greear
2017-10-04 8:50 ` Kalle Valo
2017-10-04 11:33 ` Sebastian Gottschall
2017-10-04 15:13 ` Ben Greear [this message]
2017-10-04 16:35 ` Sebastian Gottschall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78f5383d-0187-628e-cf56-de6234fdb9b0@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=s.gottschall@dd-wrt.com \
--cc=s.pooheer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox