From: Kalle Valo <kalle.valo@iki.fi>
To: Bob Copeland <me@bobcopeland.com>
Cc: linux-wireless@vger.kernel.org, pierre@ossman.eu, san@google.com
Subject: Re: [PATCH/RFC 0/7] wl12xx SDIO interface
Date: Thu, 11 Jun 2009 18:54:47 +0300 [thread overview]
Message-ID: <874oumyddk.fsf@litku.valot.fi> (raw)
In-Reply-To: <1244685780-28930-1-git-send-email-me@bobcopeland.com> (Bob Copeland's message of "Wed\, 10 Jun 2009 22\:02\:53 -0400")
Bob Copeland <me@bobcopeland.com> writes:
> Here's v2 of the SDIO interface for wl12xx, still with a FIXME or two.
>
> For my part, this is mainly a port of the Google/TI Android SDIO
> interface logic to the existing SPI driver. I have confirmed that
> the driver associates and sends some traffic.
I quickly read the patches and they look really good. Thanks a lot for
your work on this, you have done a great job.
About the plan how to merge these. I have quite a big pile of patches
pending for submission and I hope to send them either tomorrow or latest
on Monday. Unfortunately the patches will conflict your patches, but I
can rebase your sdio patches on top of my patches. It shouldn't take
that long. Only problem is that I don't have a device to test the SDIO,
so I might need your help with that.
Sorry about the mess, I have been sitting on top of the wl1251 patches
way too long.
--
Kalle Valo
next prev parent reply other threads:[~2009-06-11 15:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 2:02 [PATCH/RFC 0/7] wl12xx SDIO interface Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 1/7] wl12xx: separate bus i/o code into io.c Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 2/7] wl12xx: use wiphy_dev instead of wl->spi->dev Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 3/7] wl12xx: introduce wl12xx_if_operations struct Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 4/7] wl12xx: make wl12xx_set_partition bus agnostic Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 5/7] wl12xx: move module probe methods into spi.c Bob Copeland
2009-06-11 2:02 ` [PATCH/RFC 6/7] wl12xx: split spi interface into separate module Bob Copeland
2009-06-11 2:03 ` [PATCH/RFC 7/7] wl12xx: add sdio support Bob Copeland
2009-06-13 11:21 ` Pierre Ossman
2009-06-13 16:00 ` Kalle Valo
2009-06-13 19:41 ` Marcel Holtmann
2009-06-13 20:13 ` Kalle Valo
2009-06-13 20:24 ` Marcel Holtmann
2009-06-13 20:44 ` Kalle Valo
2009-06-13 20:09 ` Pierre Ossman
2009-06-13 20:57 ` Bob Copeland
2009-06-18 2:25 ` Bob Copeland
2009-06-19 19:24 ` Pierre Ossman
2009-06-19 20:31 ` Bob Copeland
2009-06-20 4:29 ` Kalle Valo
2009-06-21 18:38 ` Pierre Ossman
2009-06-22 0:05 ` Bob Copeland
2009-06-22 6:09 ` Pierre Ossman
2009-06-22 6:14 ` Pierre Ossman
2009-06-23 2:18 ` Bob Copeland
2009-07-15 7:12 ` Ohad Ben-Cohen
2009-07-15 12:08 ` Bob Copeland
2009-06-11 14:38 ` [PATCH/RFC 0/7] wl12xx SDIO interface Gábor Stefanik
2009-06-11 14:54 ` Florian Fainelli
2009-06-11 17:06 ` Bob Copeland
2009-06-11 14:55 ` Samuel Ortiz
2009-06-11 14:59 ` Florian Fainelli
2009-06-11 15:04 ` Gábor Stefanik
2009-06-11 15:08 ` Florian Fainelli
2009-06-11 15:03 ` Samuel Ortiz
2009-06-11 15:54 ` Kalle Valo [this message]
2009-06-11 17:08 ` Bob Copeland
2009-06-11 17:14 ` Kalle Valo
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=874oumyddk.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=pierre@ossman.eu \
--cc=san@google.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).