Return-path: Received: from fg-out-1718.google.com ([72.14.220.153]:18486 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751566AbZJ1V5Q (ORCPT ); Wed, 28 Oct 2009 17:57:16 -0400 From: Bartlomiej Zolnierkiewicz To: "John W. Linville" Subject: Re: pull request: wireless-next-2.6 2009-10-28 Date: Wed, 28 Oct 2009 22:56:00 +0100 Cc: davem@davemloft.net, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20091028211031.GF2856@tuxdriver.com> In-Reply-To: <20091028211031.GF2856@tuxdriver.com> MIME-Version: 1.0 Message-Id: <200910282256.00407.bzolnier@gmail.com> Content-Type: Text/Plain; charset="iso-8859-1" Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wednesday 28 October 2009 22:10:32 John W. Linville wrote: > Dave, > > I let my patches pile-up! Yikes!! > > This request includes the usual ton of stuff for -next -- driver > updates, fixes for some earlier -next stuff, a few cfg80211 changes to > accomodate the libertas driver, etc. Of note is the rt2800pci support > added to the rt2x00 family. Unfortunately rt2800pci support is non-functioning at the moment... :( > Pleaset let me know if there are problems! I find it rather disappointing that all my review comments regarding rt2800pci support were just completely ignored and then the initial patch was merged just as it was.. The way rt2800usb and rt2800pci drivers are designed really results in making the task of adding working support for RT28x0 and RT30x0 chipsets to rt2x00 infrastructure more difficult and time consuming than it should be... :( -- Bartlomiej Zolnierkiewicz