From: Bob Copeland <me@bobcopeland.com>
To: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
linville@tuxdriver.com, jirislaby@gmail.com, mcgrof@gmail.com,
nbd@openwrt.org
Subject: Re: [PATCH] ath5k: Update PCU code
Date: Tue, 28 Oct 2008 22:46:03 -0400 [thread overview]
Message-ID: <20081029024603.GA22759@hash.localnet> (raw)
In-Reply-To: <20081029021121.GA3079@makis>
On Wed, Oct 29, 2008 at 04:11:22AM +0200, Nick Kossifidis wrote:
> * Properly clean MIC key from keytable when TKIP is used (Bob is
> working on set_key function etc so i leave it for now).
Heh, I was just prepping patches to send out. I had basically the
same thing for _reset_key too so I'll just rebase mine on top of this.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2008-10-29 2:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 2:11 [PATCH] ath5k: Update PCU code Nick Kossifidis
2008-10-29 2:28 ` Nick Kossifidis
2008-10-29 2:46 ` Bob Copeland [this message]
2008-10-29 11:08 ` [ath5k-devel] " Nick Kossifidis
2008-10-29 14:05 ` Bob Copeland
2008-10-29 14:41 ` Nick Kossifidis
2008-10-30 3:24 ` Bob Copeland
2008-10-30 21:51 ` Nick Kossifidis
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=20081029024603.GA22759@hash.localnet \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=nbd@openwrt.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).