From: Solomon Peachy <pizza@shaftnet.org>
To: linux-wireless@vger.kernel.org
Subject: [PATCH] ST-E CW1200 driver (v7)
Date: Fri, 24 May 2013 20:04:37 -0400 [thread overview]
Message-ID: <1369440291-8961-1-git-send-email-pizza@shaftnet.org> (raw)
Very little has changed since the last patch:
* Add a module paramater that disables bss loss mitigation entirely
* 3.9 compatibility
* Fix Kconfig (again)
* 3.10 compatibility
* Rebase against wireless-next
The 3.10+ changes have been compile-tested only -- Due to a move-in-
progress I'm temporarily unable to test anything.
- Solomon
next reply other threads:[~2013-05-25 0:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 0:04 Solomon Peachy [this message]
2013-05-25 0:04 ` [PATCH 01/14] cw1200: v7: Low-level hardware I/O access Solomon Peachy
2013-05-25 0:04 ` [PATCH 02/14] cw1200: v7: Internal TX queue handling & tracking Solomon Peachy
2013-05-25 0:04 ` [PATCH 03/14] cw1200: v7: Scanning implementation Solomon Peachy
2013-05-25 0:04 ` [PATCH 04/14] cw1200: v7: WoWLAN power management Solomon Peachy
2013-05-25 0:04 ` [PATCH 05/14] cw1200: v7: Firmware loading Solomon Peachy
2013-05-25 0:04 ` [PATCH 06/14] cw1200: v7: Debugging hooks and test tool support Solomon Peachy
2013-05-25 0:04 ` [PATCH 07/14] cw1200: v7: mac80211 API implementation Solomon Peachy
2013-05-25 0:04 ` [PATCH 08/14] cw1200: v7: Packet TX/RX Solomon Peachy
2013-05-25 0:04 ` [PATCH 09/14] cw1200: v7: WSM (host-firmware) interface Solomon Peachy
2013-05-25 0:04 ` [PATCH 10/14] cw1200: v7: Main processing loop Solomon Peachy
2013-05-25 0:04 ` [PATCH 11/14] cw1200: v7: Common definitions, state, and registration handling Solomon Peachy
2013-05-25 0:04 ` [PATCH 12/14] cw1200: v7: Platform definitions, plus SDIO and SPI bus glue code Solomon Peachy
2013-05-25 0:04 ` [PATCH 13/14] cw1200: v7: Module containing platform data for Sagrad SG901-1091/1098 devices Solomon Peachy
2013-05-25 0:04 ` [PATCH 14/14] cw1200: v7: Kbuild integration and maintainers entry Solomon Peachy
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=1369440291-8961-1-git-send-email-pizza@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=linux-wireless@vger.kernel.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