From: David Kilroy <kilroyd@googlemail.com>
To: linux-wireless@vger.kernel.org
Cc: orinoco-devel@lists.sourceforge.net,
David Kilroy <kilroyd@googlemail.com>
Subject: [PATCH 0/6] orinoco: preliminary refactorring before cfg80211 key handling
Date: Wed, 5 Aug 2009 21:23:26 +0100 [thread overview]
Message-ID: <1249503812-16921-1-git-send-email-kilroyd@googlemail.com> (raw)
This series does a little clean up, moves a few common routines which we
will need in the cfg80211 handlers to hw.c, and puts all our keys in one
basket.
These have been running for a while on my machine, and I haven't noticed
any breakage.
Signed-off-by: David Kilroy <kilroyd@googlemail.com>
---
David Kilroy (6):
orinoco: prefer_port3 can be a single bit
orinoco: use local types for auth alg and sequence length
orinoco: pass orinoco_set_tkip_key the sequence lengths
orinoco: move disassociation to hw.c
orinoco: add function to retrieve current bssid
orinoco: consolidate storage of WEP and TKIP keys
drivers/net/wireless/orinoco/hw.c | 120 +++++++++++++++++-----
drivers/net/wireless/orinoco/hw.h | 7 +-
drivers/net/wireless/orinoco/main.c | 35 ++++--
drivers/net/wireless/orinoco/orinoco.h | 16 ++-
drivers/net/wireless/orinoco/wext.c | 173 +++++++++++++++++++-------------
5 files changed, 236 insertions(+), 115 deletions(-)
next reply other threads:[~2009-08-05 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 20:23 David Kilroy [this message]
2009-08-05 20:23 ` [PATCH 1/6] orinoco: prefer_port3 can be a single bit David Kilroy
2009-08-05 20:23 ` [PATCH 2/6] orinoco: use local types for auth alg and sequence length David Kilroy
2009-08-05 20:23 ` [PATCH 3/6] orinoco: pass orinoco_set_tkip_key the sequence lengths David Kilroy
2009-08-05 20:23 ` [PATCH 4/6] orinoco: move disassociation to hw.c David Kilroy
2009-08-05 20:23 ` [PATCH 5/6] orinoco: add function to retrieve current bssid David Kilroy
2009-08-05 20:23 ` [PATCH 6/6] orinoco: consolidate storage of WEP and TKIP keys David Kilroy
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=1249503812-16921-1-git-send-email-kilroyd@googlemail.com \
--to=kilroyd@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=orinoco-devel@lists.sourceforge.net \
/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