From: Solomon Peachy <pizza@shaftnet.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 12/15] cw1200: v5: Platform definitions, plus SDIO and SPI bus glue code
Date: Wed, 27 Mar 2013 11:53:07 -0400 [thread overview]
Message-ID: <20130327155306.GA20103@shaftnet.org> (raw)
In-Reply-To: <CACRpkdabdiA=bQX3nCyB2jP2hDQq0SEqVXqF1myN1jswXT2e6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
On Wed, Mar 27, 2013 at 02:05:27PM +0100, Linus Walleij wrote:
> > drivers/net/wireless/cw1200/cw1200_sdio.c | 415 ++++++++++++++++++++++++++
> > drivers/net/wireless/cw1200/cw1200_spi.c | 470 ++++++++++++++++++++++++++++++
> > include/linux/cw1200_platform.h | 46 +++
>
> I think platform data shall be in
> include/linux/platform_data/wireless-cw1200.h these
> days.
Hmm. I'll fix this for the next submission.
FWIW there are still a handful of platform files under include/linux,
and the compat-driver tree I'm developing against doesn't even have a
include/linux/platform-data directory. :)
> Apart from that I do not understand WLAN drivers, sorry :-)
Thanks for the comments all the same, every bit of review helps.
- 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-03-27 15:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 22:39 RFCv5: ST-E CW1200 WLAN driver Solomon Peachy
2013-03-21 22:39 ` [PATCH 01/15] cw1200: v5: Low-level hardware I/O access Solomon Peachy
2013-03-21 22:39 ` [PATCH 02/15] cw1200: v5: Internal TX queue handling & tracking Solomon Peachy
2013-03-21 22:39 ` [PATCH 03/15] cw1200: v5: Scanning implementation Solomon Peachy
2013-03-21 22:39 ` [PATCH 04/15] cw1200: v5: Power Management (WoWLAN) Solomon Peachy
2013-03-21 22:39 ` [PATCH 05/15] cw1200: v5: Firmware loading Solomon Peachy
2013-03-21 22:39 ` [PATCH 06/15] cw1200: v5: Debugging hooks and test tool support Solomon Peachy
2013-03-21 22:39 ` [PATCH 07/15] cw1200: v5: mac80211 API implementation Solomon Peachy
2013-03-21 22:39 ` [PATCH 08/15] cw1200: v5: Packet TX/RX Solomon Peachy
2013-03-21 22:39 ` [PATCH 09/15] cw1200: v5: WSM (host-firmware) interface Solomon Peachy
2013-03-21 22:39 ` [PATCH 10/15] cw1200: v5: Main processing loop Solomon Peachy
2013-03-21 22:39 ` [PATCH 11/15] cw1200: v5: common state, definitions, and registration handling Solomon Peachy
2013-03-21 22:39 ` [PATCH 12/15] cw1200: v5: Platform definitions, plus SDIO and SPI bus glue code Solomon Peachy
2013-03-27 13:05 ` Linus Walleij
2013-03-27 15:53 ` Solomon Peachy [this message]
2013-03-21 22:39 ` [PATCH 13/15] cw1200: v5: Module defining platform data for Sagrad SG901-1091/1098 modules Solomon Peachy
2013-03-21 22:39 ` [PATCH 14/15] cw1200: v5: Kbuild integration Solomon Peachy
2013-03-21 22:39 ` [PATCH 15/15] cw1200: v5: Add MAINTAINERS entry and add to drivers/net/wireless build Solomon Peachy
2013-04-02 19:13 ` RFCv5: ST-E CW1200 WLAN driver Solomon Peachy
2013-04-05 11:51 ` Pontus Fuchs
2013-04-27 12:27 ` Solomon Peachy
2013-04-27 17:53 ` Johannes Berg
2013-04-28 1:38 ` 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=20130327155306.GA20103@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=linus.walleij@linaro.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;
as well as URLs for NNTP newsgroup(s).