From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: davem@davemloft.net
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: pull request: wireless-next-2.6 2009-10-28
Date: Thu, 29 Oct 2009 12:12:41 +0100 [thread overview]
Message-ID: <200910291212.41656.bzolnier@gmail.com> (raw)
In-Reply-To: <200910282256.00407.bzolnier@gmail.com>
On Wednesday 28 October 2009 22:56:00 Bartlomiej Zolnierkiewicz wrote:
> 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... :(
What is even more disappointing (especially after all that "working with"
preaching) is that the patch is now in net-next-2.6..
--
Bartlomiej Zolnierkiewicz
next prev parent reply other threads:[~2009-10-29 11:13 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 21:10 pull request: wireless-next-2.6 2009-10-28 John W. Linville
2009-10-28 21:56 ` Bartlomiej Zolnierkiewicz
2009-10-29 11:12 ` Bartlomiej Zolnierkiewicz [this message]
2009-10-29 12:15 ` David Miller
2009-10-29 12:15 ` David Miller
2009-10-29 12:45 ` Bartlomiej Zolnierkiewicz
2009-10-29 12:45 ` Bartlomiej Zolnierkiewicz
2009-10-29 12:59 ` David Miller
2009-10-29 12:59 ` David Miller
2009-10-29 13:35 ` Bartlomiej Zolnierkiewicz
2009-10-29 13:52 ` Pekka Enberg
2009-10-29 14:14 ` Bartlomiej Zolnierkiewicz
2009-10-29 14:21 ` David Miller
2009-10-29 14:39 ` Michael Buesch
2009-10-29 14:39 ` Michael Buesch
2009-10-29 14:44 ` Gertjan van Wingerde
2009-10-29 14:48 ` Michael Buesch
2009-10-29 14:48 ` Michael Buesch
2009-10-29 15:08 ` Luis R. Rodriguez
2009-10-29 15:08 ` Luis R. Rodriguez
2009-10-29 17:49 ` Bartlomiej Zolnierkiewicz
2009-10-29 19:45 ` Pekka Enberg
2009-10-29 21:48 ` Bartlomiej Zolnierkiewicz
2009-10-29 21:48 ` Bartlomiej Zolnierkiewicz
2009-10-30 5:59 ` Pekka Enberg
2009-10-30 5:59 ` Pekka Enberg
2009-10-30 7:00 ` Johannes Berg
2009-10-30 11:06 ` Jarek Poplawski
2009-10-30 15:02 ` John W. Linville
2009-10-30 15:02 ` John W. Linville
2009-10-30 20:44 ` Jarek Poplawski
2009-10-30 20:44 ` Jarek Poplawski
2009-11-01 19:04 ` Bartlomiej Zolnierkiewicz
2009-11-01 19:04 ` Bartlomiej Zolnierkiewicz
2009-11-02 9:10 ` Ingo Molnar
2009-11-02 9:23 ` Johannes Berg
2009-11-02 10:07 ` Ingo Molnar
2009-11-02 17:01 ` John W. Linville
2009-11-02 17:01 ` John W. Linville
2009-11-02 17:32 ` Luis Correia
2009-11-02 17:36 ` Randy Dunlap
2009-11-02 18:29 ` John W. Linville
2009-11-02 18:29 ` John W. Linville
2009-11-02 18:43 ` Ivo van Doorn
2009-11-02 18:43 ` Ivo van Doorn
2009-11-03 19:59 ` Bartlomiej Zolnierkiewicz
2009-11-03 20:32 ` Ivo van Doorn
2009-11-03 21:04 ` Bartlomiej Zolnierkiewicz
2009-11-02 21:16 ` Pavel Machek
2009-11-04 13:03 ` Jiri Kosina
2009-11-04 21:17 ` Ivo van Doorn
2009-11-04 21:17 ` Ivo van Doorn
2009-11-04 22:00 ` Pavel Machek
2009-11-04 22:09 ` John W. Linville
2009-11-02 16:46 ` John W. Linville
2009-10-30 15:14 ` John W. Linville
2009-10-29 13:53 ` David Miller
2009-10-29 14:13 ` Bartlomiej Zolnierkiewicz
2009-10-29 14:13 ` Bartlomiej Zolnierkiewicz
2009-10-29 14:20 ` David Miller
2009-10-29 14:20 ` David Miller
2009-10-29 14:24 ` Johannes Berg
2009-10-29 14:34 ` Bartlomiej Zolnierkiewicz
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=200910291212.41656.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.