From: Antonio Quartulli <antonio@open-mesh.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath9k pending patches
Date: Wed, 27 Nov 2013 13:31:09 +0100 [thread overview]
Message-ID: <5295E60D.90600@open-mesh.com> (raw)
In-Reply-To: <21141.51790.303263.385517@gargle.gargle.HOWL>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Sujith,
On 27/11/13 11:32, Sujith Manoharan wrote:
What patch is addressing this change? And can could please explain a
bit more about what is needed to address the key cache corruption problem?
Right now I am working on a "reactive behavior" which tries to detect
a cache corruption event and subsequently re-install all the keys one
by one to ensure they are back to a proper state.
What does this ALWAYS_PERFORM_KEY_SEARCH bit do? Is it set within the
initvalues?
Sorry for shooting all these questions at once, but I am really trying
to understand how to properly address this issue.
Cheers,
- --
Antonio Quartulli
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBCAAGBQJSleYNAAoJEADl0hg6qKeO7p4P/RBa9tGDY1xYTTlHNATh4WfX
kIIPdM7x8/+S/wQPKndZ4TPJpBjsnXVnSMhcjMDjbepFRmx40FcElj/ObvKhB3Mc
lMawsFyCEQHjUdNbSS01c3DYmbxw1YM1DUPl2N2XQKaiXbd8Zz7Rr71k8npDt07C
3LScQeiWvj6TOwP89hXnfz2sBRPkhA4z1rTP7omr3CV9N8Ik6E23LsUnijgG8bgI
w5XZ4NGZaVn75TdTsdk8wFm853R2/on5rb0CACHV9Z7T/oT8QM3fKMhEV6pR97wI
P1Titinssw65ycOHlMcGmUi0DoFZHQUuI6LX2V4o5Vr1nsYN8WkQiRu7iy8MiESO
nLdxK+5VKXL0Tf3roN3CxBzINwE9GsL2EmkvjtUZy4SdAGB7H5+QCs+/XBhB3aTH
eeJo2nVdFGNNhrTOfdUdNfpwYvwwAzMHBYxARwifPG3g718a/xSlSsjDDTuSY7+x
656CD7Nbuq3JzVlfM//QEOb07N9xuEcXiSDdghY7GsJzBN+T2eS6vG57S/V4/ecj
1n7opm+f0+2vjZs/SGiykKyphWFuKY89TAXA67bP91qmYLmrdZccJtrqv/zEhfqO
Z1lXYvM1X5SAb5Kbmj/8YPz/ZdmGxGSDRVQa8f4ujXCZ8gR4gA6eNkGprPljos6N
LSZyNHlxM8Adgx20NC/+
=ONks
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-11-27 12:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 10:23 [PATCH 0/2] ath9k initval updates Sujith Manoharan
2013-11-27 10:23 ` [PATCH 1/2] ath9k: Update initvals for AR9300 v2.2 Sujith Manoharan
2013-11-27 10:23 ` [PATCH 2/2] ath9k: Update initvals for AR9580 v1.0 Sujith Manoharan
2013-11-27 10:32 ` ath9k pending patches Sujith Manoharan
2013-11-27 12:31 ` Antonio Quartulli [this message]
2013-11-27 15:20 ` Sujith Manoharan
2013-11-27 15:42 ` Antonio Quartulli
2013-11-27 12:52 ` Antonio Quartulli
2013-11-27 15:33 ` Sujith Manoharan
2013-11-27 15:43 ` Antonio Quartulli
2013-11-27 15:58 ` Antonio Quartulli
2013-11-27 16:00 ` Felix Fietkau
2013-11-27 16:34 ` Sujith Manoharan
-- strict thread matches above, loose matches on Subject: below --
2013-09-16 6:04 Sujith Manoharan
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=5295E60D.90600@open-mesh.com \
--to=antonio@open-mesh.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.org \
/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).