Date: Fri, 11 Jan 2013 10:58:08 -0500
From: Solomon Peachy <pizza@shaftnet.org>
To: linux-wireless@vger.kernel.org
Subject: Re: RFCv2: ST-E cw1200 driver
Message-ID: <20130111155807.GA5153@shaftnet.org> (sfid-20130111_165814_857210_A792E6CA)
References: <1356218312-13616-1-git-send-email-pizza@shaftnet.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS"
In-Reply-To: <1356218312-13616-1-git-send-email-pizza@shaftnet.org>
Sender: linux-wireless-owner@vger.kernel.org


--qMm9M+Fa2AknHoGS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 22, 2012 at 06:18:15PM -0500, Solomon Peachy wrote:
> Okay, here's the second pass.  Changes from v1:

Now that I've been getting some third-party test results, I'm planning=20
on posting a v3 patch series this weekend.

Any further comments before I do so?  Should I stick to the staging=20
area, or should I move it over to drivers/net/wireless?

(The only known problem is that IBSS is still broken, but now it merely=20
 doesn't work properly instead of triggering OOPSen -- still trying to=20
 track that down but I've been sidetracked by other OMGURGENT!!11 tasks)

 - Solomon
--=20
Solomon Peachy        		       pizza at shaftnet dot org	=20
Melbourne, FL                          ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur.

--qMm9M+Fa2AknHoGS
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iD8DBQFQ8DaPPuLgii2759ARAggTAKCOOFbkcnG39SCUsQVimRlnlUvXagCeIDED
8rL0WUm3HWJ2XpyuWFoTwNw=
=5Ajy
-----END PGP SIGNATURE-----

--qMm9M+Fa2AknHoGS--