From: Solomon Peachy <pizza@shaftnet.org>
To: Bartosz Markowski <markowski.bartosz@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RFCv4: ST-E CW1100/1200 WLAN driver
Date: Wed, 20 Mar 2013 07:53:35 -0400 [thread overview]
Message-ID: <20130320115334.GA816@shaftnet.org> (raw)
In-Reply-To: <CAM8CFPibkQRrKtekdduZ_eA7rRoqbFp6UR6vr0a8QkgkXi4RxA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
On Wed, Mar 20, 2013 at 09:10:14AM +0100, Bartosz Markowski wrote:
> Is the upstream process dropped or you plan to continue in the near future?
At least as far as I'm concerned, the upstreaming process is still
ongoing. The last major holdup from that perspective was the
voluminious pile of checkpatch warnings.
There's also been a surprising amount of non-trivial development going
on too, and I wanted to take the time to let the testing shake loose bugs.
Over the past two weeks I've been distracted with other goings-on, but
that's all sorted now and I expect to be able to submit another patch set
by Friday.
- 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 --]
prev parent reply other threads:[~2013-03-20 11:53 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
2013-03-20 8:10 ` Bartosz Markowski
2013-03-20 11:53 ` Solomon Peachy [this message]
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=20130320115334.GA816@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=linux-wireless@vger.kernel.org \
--cc=markowski.bartosz@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).