From: Samuel Ortiz <sameo@linux.intel.com>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, Zhu Yi <yi.zhu@intel.com>
Subject: [PATCH 00/11 v2] iwmc3200wifi updates
Date: Mon, 15 Jun 2009 21:36:12 +0200 [thread overview]
Message-ID: <cover.1245091931.git.samuel@sortiz.org> (raw)
Hi John,
Here go some updates for the iwmc3200wifi driver.
Some of those patches are bug fixes and we'd like them to eventually make it
to 2.6.31. The rest are targeted at wireless-testing inclusion.
I tried to set an explicit subject line to let you clearly understand where
we'd like each of them to land, please let me know if that's not the case.
Changes:
v2: Removed patch #1 from the previous patch set.
With patch #3 (#2 on patch set v2), we are actually registering the netdev
_after_ the SDIO bus is really ready.
Samuel Ortiz (4):
iwmc3200wifi: invalidate keys when changing the BSSID
iwmc3200wifi: handling wifi_if_ntfy responses
iwmc3200wifi: cfg80211 key hooks implemetation
iwmc3200wifi: cache keys when interface is down
Zhu Yi (7):
iwmc3200wifi: check for iwm_priv_init error
iwmc3200wifi: add iwm_if_add and iwm_if_remove
iwmc3200wifi: fix potential kernel oops on module removal
iwmc3200wifi: add a mutex to protect iwm_reset_worker
iwmc3200wifi: change coexist periodic calibration flag
iwmc3200wifi: remove select LIB80211 from Kconfig
iwmc3200wifi: rfkill cleanup
drivers/net/wireless/iwmc3200wifi/Kconfig | 1 -
drivers/net/wireless/iwmc3200wifi/cfg80211.c | 204 +++++++++++++++++
drivers/net/wireless/iwmc3200wifi/commands.c | 116 +++++------
drivers/net/wireless/iwmc3200wifi/commands.h | 7 +-
drivers/net/wireless/iwmc3200wifi/iwm.h | 28 ++--
drivers/net/wireless/iwmc3200wifi/main.c | 89 ++++++--
drivers/net/wireless/iwmc3200wifi/netdev.c | 72 ++++---
drivers/net/wireless/iwmc3200wifi/rx.c | 27 ++-
drivers/net/wireless/iwmc3200wifi/sdio.c | 17 +-
drivers/net/wireless/iwmc3200wifi/umac.h | 2 +
drivers/net/wireless/iwmc3200wifi/wext.c | 305 +++-----------------------
11 files changed, 443 insertions(+), 425 deletions(-)
next reply other threads:[~2009-06-15 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 19:36 Samuel Ortiz [this message]
2009-06-15 19:36 ` [PATCH 01/11 v2][2.6.31 and w-t] iwmc3200wifi: check for iwm_priv_init error Samuel Ortiz
2009-06-15 19:36 ` [PATCH 02/11 v2][2.6.31 and w-t] iwmc3200wifi: add iwm_if_add and iwm_if_remove Samuel Ortiz
2009-06-15 19:59 ` [PATCH 03/11 v2][2.6.31 and w-t] iwmc3200wifi: fix potential kernel oops on module removal Samuel Ortiz
2009-06-15 19:59 ` [PATCH 04/11 v2][2.6.31 and w-t] iwmc3200wifi: add a mutex to protect iwm_reset_worker Samuel Ortiz
2009-06-15 19:59 ` [PATCH 05/11 v2][w-t] iwmc3200wifi: invalidate keys when changing the BSSID Samuel Ortiz
2009-06-15 19:59 ` [PATCH 06/11 v2][w-t] iwmc3200wifi: handling wifi_if_ntfy responses Samuel Ortiz
2009-06-15 19:59 ` [PATCH 07/11 v2][w-t] iwmc3200wifi: cfg80211 key hooks implemetation Samuel Ortiz
2009-06-15 19:59 ` [PATCH 08/11 v2][w-t] iwmc3200wifi: change coexist periodic calibration flag Samuel Ortiz
2009-06-15 19:59 ` [PATCH 09/11 v2][w-t] iwmc3200wifi: cache keys when interface is down Samuel Ortiz
2009-06-15 19:59 ` [PATCH 10/11 v2][w-t] iwmc3200wifi: remove select LIB80211 from Kconfig Samuel Ortiz
2009-06-15 19:59 ` [PATCH 11/11 v2][w-t] iwmc3200wifi: rfkill cleanup Samuel Ortiz
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=cover.1245091931.git.samuel@sortiz.org \
--to=sameo@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=yi.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).