From: Solomon Peachy <pizza@shaftnet.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Pontus Fuchs <pontus.fuchs@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: RFCv3: ST-E CW1200 WLAN driver
Date: Wed, 30 Jan 2013 17:32:32 -0500 [thread overview]
Message-ID: <20130130223232.GA7307@shaftnet.org> (raw)
In-Reply-To: <20130130190215.GA2167@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On Wed, Jan 30, 2013 at 02:02:16PM -0500, John W. Linville wrote:
> > I believe this driver should go into driver/net/wireless considering
> > that we have a maintainer, it has passed wifi cert and is in use in
> > production devices.
> >
> > I have a few patches queued up for you that fixes the last sparse
> > warnings too...
>
> Solomon, do you agree with this? Are you going to repost again?
Yes, I have already moved the driver over into net/wireless in my tree,
plus a nontrivial pile of changes has occured since v3. I hope to
post v4 by this weekend.
This is my current to-do list:
* One final Kconfig option to eliminate
* A possible crash (reported not three hours ago) that needs confirming
* Hot unplug is still iffy (but better!)
* Reworked SPI interrupt delivery completely untested
* IBSS is still busted (haven't had time to tackle it properly)
* Rebase against 3.8
* Investigate adding OF bindings that can be used instead of platform_data
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Melbourne, FL ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2013-01-30 22:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 14:06 RFCv3: ST-E CW1200 WLAN driver Solomon Peachy
2013-01-12 14:06 ` [PATCH 01/15] cw1200: v3: low-level hadrware I/O functions Solomon Peachy
2013-01-12 14:06 ` [PATCH 02/15] cw1200: v3: internal tx queue handling and tracking Solomon Peachy
2013-01-12 14:06 ` [PATCH 03/15] cw1200: v3: scanning implementation Solomon Peachy
2013-01-12 14:06 ` [PATCH 04/15] cw1200: v3: power management Solomon Peachy
2013-01-12 14:06 ` [PATCH 05/15] cw1200: v3: firmware loading Solomon Peachy
2013-01-12 14:06 ` [PATCH 06/15] cw1200: v3: mini-ap support code Solomon Peachy
2013-01-12 14:06 ` [PATCH 07/15] cw1200: v3: debugging hooks and test tool support Solomon Peachy
2013-01-12 14:06 ` [PATCH 08/15] cw1200: v3: 802.11 station API Solomon Peachy
2013-01-12 14:06 ` [PATCH 09/15] cw1200: v3: packet transmit and receiving Solomon Peachy
2013-01-12 14:06 ` [PATCH 10/15] cw1200: v3: WSM (host-firmware) interface glue Solomon Peachy
2013-01-12 14:06 ` [PATCH 11/15] cw1200: v3: main processing loop Solomon Peachy
2013-01-12 14:06 ` [PATCH 12/15] cw1200: v3: common state, definitions, and registration handling Solomon Peachy
2013-01-12 14:06 ` [PATCH 13/15] cw1200: v3: SDIO and SPI glue code and platform definitions Solomon Peachy
2013-01-12 14:06 ` [PATCH 14/15] cw1200: v3: Kbuild integration Solomon Peachy
2013-01-12 14:06 ` [PATCH 15/15] cw1200: v3: Add to drivers/staging, and a MAINTAINERS entry Solomon Peachy
2013-01-14 12:17 ` RFCv3: ST-E CW1200 WLAN driver Pontus Fuchs
2013-01-30 19:02 ` John W. Linville
2013-01-30 22:32 ` Solomon Peachy [this message]
2013-02-01 1:54 ` Solomon Peachy
2013-02-07 4:21 ` 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=20130130223232.GA7307@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pontus.fuchs@gmail.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).