From: Kalle Valo <kvalo@codeaurora.org>
To: Antonio Quartulli <a@unstable.cc>
Cc: ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org,
sw@simonwunderlich.de, Antonio Quartulli <antonio@open-mesh.com>
Subject: Re: [NOT FOR MERGE] ath9k: work around key cache corruption
Date: Wed, 26 Oct 2016 17:05:14 +0300 [thread overview]
Message-ID: <87lgxbxl2d.fsf@purkki.adurom.net> (raw)
In-Reply-To: <20161018083552.28592-1-a@unstable.cc> (Antonio Quartulli's message of "Tue, 18 Oct 2016 16:35:52 +0800")
Antonio Quartulli <a@unstable.cc> writes:
> From: Antonio Quartulli <antonio@open-mesh.com>
>
> This patch was crafted long time ago to work around a key cache
> corruption problem on ath9k chipsets.
>
> The workaround consists in periodically triggering a worker that
> uploads all the keys to the HW cache. The worker is triggered also
> when the vif detects 21 undecryptable packets.
>
>
> This patch is based on top compat-wireless-2015-10-26.
>
>
> I was asked to release this code to the public and, since it is
> GPL, I am now doing it.
GPL? AFAICS ath9k is under ISC. I'm not sure what you mean with the
sentence above, but it's possible to interpret it so that this patch is
not under ISC license, which is problematic.
--
Kalle Valo
next prev parent reply other threads:[~2016-10-26 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 8:35 [NOT FOR MERGE] ath9k: work around key cache corruption Antonio Quartulli
2016-10-22 13:42 ` Antonio Quartulli
2016-10-22 20:34 ` Johannes Berg
2017-01-09 8:57 ` [ath9k-devel] " Stam, Michel [FINT]
2016-10-26 14:05 ` Kalle Valo [this message]
2016-10-26 14:10 ` Antonio Quartulli
2016-10-27 6:02 ` Kalle Valo
2016-10-27 7:54 ` Sebastian Gottschall
2016-10-27 15:06 ` Johannes Berg
2016-11-14 12:50 ` [ath9k-devel] " Stam, Michel [FINT]
2016-11-14 23:25 ` Adrian Chadd
2016-11-16 8:54 ` Stam, Michel [FINT]
2016-10-26 14:43 ` Ferry Huberts
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=87lgxbxl2d.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=a@unstable.cc \
--cc=antonio@open-mesh.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sw@simonwunderlich.de \
/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;
as well as URLs for NNTP newsgroup(s).