From: "John W. Linville" <linville@tuxdriver.com>
To: Luis Correia <luis.f.correia@gmail.com>
Cc: "Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>,
"Dan Williams" <dcbw@redhat.com>,
"Ivo van Doorn" <ivdoorn@gmail.com>,
"Ozan Çağlayan" <ozan@pardus.org.tr>,
linux-wireless@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current status of rt2800usb and staging/rt2870
Date: Wed, 14 Oct 2009 10:14:06 -0400 [thread overview]
Message-ID: <20091014141405.GB2890@tuxdriver.com> (raw)
In-Reply-To: <efe7343f0910131521u608d66f5r670dd1cf00322d0b@mail.gmail.com>
On Tue, Oct 13, 2009 at 11:21:53PM +0100, Luis Correia wrote:
> Since some days now, we have someone in the team which works for
> Ralink, I'm hopefull that he can find some time to help us make the
> driver better.
This (I hope) is the future. If we can get the vendors to cooperate
with us at this level then we can eliminate the vendor/upstream
driver distinction.
While I try to be ambivalent about drivers/staging, I _do_ think that
it tends to enable vendors to get aways with _less_ support of the
community by facilitating them in taking advantage of the "pragmatic"
among us.
> And now, i'm going back to my lovely hole, having added nothing to
> this conversation.
I disagree! :-)
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-10-14 14:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 11:24 Current status of rt2800usb and staging/rt2870 Ozan Çağlayan
2009-10-13 15:52 ` Ivo van Doorn
2009-10-13 17:27 ` Bartlomiej Zolnierkiewicz
2009-10-13 18:17 ` Ivo van Doorn
2009-10-13 19:21 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:00 ` Ivo van Doorn
2009-10-13 20:42 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:15 ` Dan Williams
2009-10-13 21:57 ` Bartlomiej Zolnierkiewicz
2009-10-13 22:21 ` Luis Correia
2009-10-14 14:14 ` John W. Linville [this message]
2009-10-13 22:24 ` Dan Williams
2009-10-13 22:42 ` Bartlomiej Zolnierkiewicz
2009-10-14 14:15 ` John W. Linville
2009-10-14 13:51 ` Ivo van Doorn
2009-10-14 14:09 ` John W. Linville
2009-10-14 14:52 ` Bartlomiej Zolnierkiewicz
2009-10-14 14:56 ` John W. Linville
2009-10-14 15:28 ` Bartlomiej Zolnierkiewicz
2009-10-14 16:47 ` John W. Linville
2009-10-14 17:33 ` Bartlomiej Zolnierkiewicz
2009-10-14 18:26 ` Luis Correia
2009-10-14 20:41 ` Bartlomiej Zolnierkiewicz
2009-10-14 18:56 ` Ivo van Doorn
2009-10-14 20:10 ` Bartlomiej Zolnierkiewicz
2009-10-15 6:28 ` Gertjan van Wingerde
2009-10-15 9:47 ` Bartlomiej Zolnierkiewicz
2009-10-14 16:55 ` Luis R. Rodriguez
2009-10-15 14:47 ` Bartlomiej Zolnierkiewicz
2009-10-15 19:06 ` Luis R. Rodriguez
2009-10-16 17:13 ` Bartlomiej Zolnierkiewicz
2009-10-14 1:52 ` Mike Galbraith
2009-10-13 16:44 ` Bartlomiej Zolnierkiewicz
2009-10-13 20:41 ` Ozan Çağlayan
2009-10-13 20:44 ` 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=20091014141405.GB2890@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bzolnier@gmail.com \
--cc=dcbw@redhat.com \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luis.f.correia@gmail.com \
--cc=ozan@pardus.org.tr \
/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).