From: "John W. Linville" <linville@tuxdriver.com>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Greg KH <greg@kroah.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
dcbw@redhat.com, linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] Add vt6656 driver to drivers/staging.
Date: Mon, 20 Apr 2009 09:59:40 -0400 [thread overview]
Message-ID: <20090420135940.GB3369@tuxdriver.com> (raw)
In-Reply-To: <200904182318.56512.IvDoorn@gmail.com>
On Sat, Apr 18, 2009 at 11:18:56PM +0200, Ivo van Doorn wrote:
> Hi,
>
> > > I hope rt2800pci/usb to be included *ASAP*, because rt2800usb supports
> > > more than 1oo USB devices and rt2800pci is included in a lot of
> > > laptops(ask Torvalds [1] [2])
> > >
> > > [1] http://marc.info/?l=linux-netdev&m=121799144422863&w=2
> > > [2] http://marc.info/?l=linux-kernel&m=123187052023831&w=2
> >
> > That would be great to have in, what's keeping it from happening?
>
> In short: A stable workable driver.
>
> The rt2800usb driver is pretty far (at least on my testsetup), but
> still has problems with transmitting frames immediately after
> association.
I read this as "it works, but some frames are lost immediately after
association" -- is that right? FWIW, this sounds good enough to me
to get it into the mainline kernel. _Please_ submit the rt2800usb
driver for wireless-testing/linux-next ASAP!
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:[~2009-04-20 14:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 19:16 [PATCH] Add vt6656 driver to drivers/staging Xose Vazquez Perez
2009-04-15 21:21 ` Greg KH
2009-04-16 5:58 ` Kalle Valo
2009-04-16 8:39 ` Max Filippov
2009-04-16 8:47 ` Kalle Valo
2009-04-16 9:14 ` Max Filippov
2009-04-16 9:52 ` Kalle Valo
2009-04-18 21:18 ` Ivo van Doorn
2009-04-20 13:59 ` John W. Linville [this message]
2009-04-21 10:30 ` Ivo Van Doorn
2009-04-21 12:42 ` Ivo Van Doorn
2009-04-21 13:53 ` John W. Linville
2009-04-21 13:52 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2009-04-14 10:52 Forest Bond
2009-04-14 11:07 ` Johannes Berg
2009-04-14 11:39 ` Forest Bond
2009-04-14 11:48 ` Johannes Berg
2009-04-14 12:28 ` Marcel Holtmann
2009-04-14 12:43 ` Johannes Berg
2009-04-14 13:02 ` John W. Linville
2009-04-14 14:19 ` Forest Bond
2009-04-15 1:10 ` Greg KH
2009-04-15 1:51 ` Forest Bond
2009-04-19 17:09 ` Forest Bond
2009-04-19 19:52 ` Larry Finger
2009-04-19 20:01 ` Forest Bond
2009-04-19 22:32 ` Greg KH
2009-04-24 11:03 ` Forest Bond
2009-04-24 14:44 ` Larry Finger
2009-04-24 14:54 ` Forest Bond
2009-04-24 22:58 ` Greg KH
2009-04-25 0:08 ` Forest Bond
2009-04-25 0:14 ` Greg KH
2009-04-15 15:43 ` Dan Williams
2009-04-16 2:51 ` Greg KH
2009-04-15 13:19 ` John W. Linville
2009-04-14 14:52 ` Forest Bond
[not found] ` <18916.37868.64939.574249@gargle.gargle.HOWL>
2009-04-14 15:26 ` John W. Linville
2009-06-01 16:35 ` Gábor Stefanik
2009-06-01 16:52 ` Forest Bond
2009-06-08 17:08 ` Olivier Blin
2009-06-08 17:45 ` Forest Bond
2009-06-08 18:01 ` Olivier Blin
[not found] <20090414024610.GA3924@storm.local.network>
2009-04-14 2:53 ` Greg KH
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=20090420135940.GB3369@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dcbw@redhat.com \
--cc=greg@kroah.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=xose.vazquez@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).