From: "John W. Linville" <linville@tuxdriver.com>
To: Solomon Peachy <pizza@shaftnet.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ST-E CW1200 driver (v6)
Date: Fri, 24 May 2013 13:50:02 -0400 [thread overview]
Message-ID: <20130524175001.GB2175@tuxdriver.com> (raw)
In-Reply-To: <1367090847-11937-1-git-send-email-pizza@shaftnet.org>
On Sat, Apr 27, 2013 at 03:27:13PM -0400, Solomon Peachy wrote:
> I'd love to see this finally committed upstream. There are no known
> bugs in the code, and it handles everything I (and other testers I've
> been working with) have thrown at it.
>
> Changes from the last patch series (v5):
> * Updated contact info for original author (Dmitry Tarnyagin)
> * Better documented the DPLL constants
> * Fixed more checkpatch warnings
> * Better logging in scan and bss loss state machines
> * BSS loss mitigation reimplemented (differently) due to FW bugginess
> * Reworked locking in the join code to handle rare corner cases
I'm sorry, but this just doesn't build on the current wireless-next
and I don't have enough time ATM to chase-down all the fix-ups.
Could you work that out and repost? Please also check the Kconfig
stuff, as that still seemed to be broken...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-05-24 18:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 19:27 [PATCH] ST-E CW1200 driver (v6) Solomon Peachy
2013-04-27 19:27 ` [PATCH 01/14] cw1200: v6: Low-level hardware I/O access Solomon Peachy
2013-04-27 19:27 ` [PATCH 02/14] cw1200: v6: Internal TX queue handling & tracking Solomon Peachy
2013-04-27 19:27 ` [PATCH 03/14] cw1200: v6: Scanning implemtation Solomon Peachy
2013-04-27 19:27 ` [PATCH 04/14] cw1200: v6: WoWLAN power management Solomon Peachy
2013-04-27 19:27 ` [PATCH 05/14] cw1200: v6: Firmware loading Solomon Peachy
2013-04-27 19:27 ` [PATCH 06/14] cw1200: v6: Debugging hooks and test tool support Solomon Peachy
2013-04-27 19:27 ` [PATCH 07/14] cw1200: v6: mac80211 API implementation Solomon Peachy
2013-04-27 19:27 ` [PATCH 08/14] cw1200: v6: Packet TX/RX Solomon Peachy
2013-04-27 19:27 ` [PATCH 09/14] cw1200: v6: WSM (host-firmware) interface Solomon Peachy
2013-04-27 19:27 ` [PATCH 10/14] cw1200: v6: Main processing loop Solomon Peachy
2013-04-27 19:27 ` [PATCH 11/14] cw1200: v6: Common definitions, state, and registration handling Solomon Peachy
2013-04-27 19:27 ` [PATCH 12/14] cw1200: v6: Platform definitions, plus SDIO and SPI bus glue code Solomon Peachy
2013-04-27 19:27 ` [PATCH 13/14] cw1200: v6: Module defining platform data for Sagrad SG901-1091/1098 modules Solomon Peachy
2013-04-27 19:27 ` [PATCH 14/14] cw1200: v6: Kbuild integration and MAINTAINERS entry Solomon Peachy
2013-05-03 17:54 ` John W. Linville
2013-05-03 19:32 ` Solomon Peachy
2013-05-03 20:29 ` John W. Linville
2013-05-03 19:37 ` [PATCH 14/14] cw1200: v6: Kbuild integration and MAINTAINERS entry (v2) Solomon Peachy
2013-05-24 17:50 ` John W. Linville [this message]
2013-05-24 23:36 ` [PATCH] ST-E CW1200 driver (v6) 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=20130524175001.GB2175@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pizza@shaftnet.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).