From: Solomon Peachy <pizza@shaftnet.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RFCv4: ST-E CW1100/1200 WLAN driver
Date: Thu, 14 Feb 2013 10:58:41 -0500 [thread overview]
Message-ID: <20130214155840.GA3232@shaftnet.org> (raw)
In-Reply-To: <1360355765.29851.29.camel@jlt4.sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Fri, Feb 08, 2013 at 09:36:05PM +0100, Johannes Berg wrote:
> > There are still a couple bits of code present for older (<2.6.36 and <3.2)
> > kernels, which I will strip out for inclusion in compat-drivers once
> > this is mainlined. (Is there a better process I should follow here?)
>
> You should probably just submit it without those bits for the
> wireless-next tree and then to the relevant compat-drivers patches as
> needed.
I'm now working on silencing checkpatch's complaints (about 3/4 done
now); most of them revolve around the use of CamelCase variable names
all over the place. In the process I'm doing other low-risk
opportunistic cleanups.
Once I'm done with that, I'll prepare another submission without the
backwards compability bits, rebased against wireless-next.
- 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-02-14 15:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 20:31 RFCv4: ST-E CW1100/1200 WLAN driver Solomon Peachy
2013-02-08 20:31 ` [PATCH 01/14] cw1200: v4: low-level hardware I/O functions Solomon Peachy
2013-02-09 1:15 ` Joe Perches
2013-02-11 18:53 ` Solomon Peachy
2013-02-11 19:01 ` Joe Perches
2013-02-11 19:25 ` Solomon Peachy
2013-02-12 13:35 ` Kalle Valo
2013-02-12 14:40 ` Joe Perches
2013-02-11 19:07 ` Solomon Peachy
2013-02-11 19:29 ` [PATCH] scripts: Remove Lindent and suggestions to use it Joe Perches
2013-02-08 20:31 ` [PATCH 02/14] cw1200: v4: Internal TX queue handling and tracking Solomon Peachy
2013-02-08 20:31 ` [PATCH 03/14] cw1200: v4: Scanning implementation Solomon Peachy
2013-02-08 20:31 ` [PATCH 04/14] cw1200: v4: Power Management (WoWLAN) Solomon Peachy
2013-02-08 20:31 ` [PATCH 05/14] cw1200: v4: Firmware loading Solomon Peachy
2013-02-08 20:31 ` [PATCH 06/14] cw1200: v4: Debugging hooks and test tool support Solomon Peachy
2013-02-08 20:32 ` [PATCH 07/14] cw1200: v4: mac80211 API implementation Solomon Peachy
2013-02-08 20:32 ` [PATCH 08/14] cw1200: v4: Packet TX/RX Solomon Peachy
2013-02-08 20:32 ` [PATCH 09/14] cw1200: v4: WSM (host-firmware) interface Solomon Peachy
2013-02-08 20:32 ` [PATCH 10/14] cw1200: v4: Main processing loop Solomon Peachy
2013-02-08 20:32 ` [PATCH 11/14] cw1200: v4: common state, definitions, and registration handling Solomon Peachy
2013-02-08 20:32 ` [PATCH 12/14] cw1200: v4: SDIO and SPI glue code and platform definitions Solomon Peachy
2013-02-08 20:32 ` [PATCH 13/14] cw1200: v4: Kbuild integration Solomon Peachy
2013-02-08 20:32 ` [PATCH 14/14] cw1200: v4: Add to drivers/net/wireless kbuild, plus MAINTAINERS entry Solomon Peachy
2013-02-08 20:36 ` RFCv4: ST-E CW1100/1200 WLAN driver Johannes Berg
2013-02-14 15:58 ` Solomon Peachy [this message]
2013-03-20 8:10 ` Bartosz Markowski
2013-03-20 11:53 ` 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=20130214155840.GA3232@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=johannes@sipsolutions.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.