From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dan Williams <dcbw@redhat.com>, Greg KH <greg@kroah.com>,
Kalle Valo <kalle.valo@iki.fi>,
proski@gnu.org, linux-wireless@vger.kernel.org
Subject: Re: at76_usb driver status
Date: Mon, 6 Oct 2008 17:39:09 -0400 [thread overview]
Message-ID: <20081006213909.GN3448@tuxdriver.com> (raw)
In-Reply-To: <1223325748.3778.30.camel@johannes.berg>
On Mon, Oct 06, 2008 at 10:42:28PM +0200, Johannes Berg wrote:
> On Mon, 2008-10-06 at 16:31 -0400, John W. Linville wrote:
> > On Mon, Oct 06, 2008 at 04:12:20PM -0400, Dan Williams wrote:
> > > On Mon, 2008-10-06 at 11:35 -0700, Greg KH wrote:
> >
> > > > I'll gladly drop it from drivers/staging when the "real" version hits
> > > > mainline, until then, it should stay in staging, as that is the whole
> > > > point of it.
> > >
> > > It does nobody any good if (a) the drivers are _never_ going to go
> > > upstream, and (b) if the drivers aren't going to get any attention in
> > > their current form because of (a).
> > >
> > > I don't care if the driver allows peoples hardware to work; I want a
> > > driver that makes peoples hardware work _well_. Out of tree drivers
> > > that are never going upstream will not work well.
> >
> > I think/thought the main point of -staging was to give drivers
> > visibility in hopes of people working to fix them.
>
> Shouldn't then the mac80211-based at76_usb be in -staging instead? That
> one might not work completely, but at least it's fixable without a
> rewrite.
Yes, probably so. That is what I had planned to send to Greg, but I
was thinking that the version currently in wireless-testing probably
won't compile against -staging (which is based on 2.6.27).
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-10-06 21:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 21:07 at76_usb driver status Greg KH
2008-10-02 16:20 ` Luis R. Rodriguez
2008-10-05 6:32 ` Kalle Valo
2008-10-05 5:56 ` Kalle Valo
2008-10-05 6:13 ` Marcel Holtmann
2008-10-05 6:22 ` Kalle Valo
2008-10-05 6:14 ` Kalle Valo
2008-10-05 6:16 ` Greg KH
2008-10-05 6:29 ` Kalle Valo
2008-10-05 15:14 ` Greg KH
2008-10-06 5:28 ` Pavel Roskin
2008-10-06 5:39 ` Kalle Valo
2008-10-06 5:42 ` Pavel Roskin
2008-10-06 6:10 ` Kalle Valo
2008-10-06 6:26 ` Pavel Roskin
2008-10-05 6:41 ` Marcel Holtmann
2008-10-05 15:14 ` Greg KH
2008-10-05 16:17 ` Marcel Holtmann
2008-10-05 22:57 ` Greg KH
2008-10-06 15:23 ` Dan Williams
2008-10-06 10:23 ` Luis R. Rodriguez
2008-10-06 18:21 ` Marcel Holtmann
2008-10-06 18:35 ` Greg KH
2008-10-06 20:12 ` Dan Williams
2008-10-06 20:31 ` John W. Linville
2008-10-06 20:42 ` Johannes Berg
2008-10-06 21:39 ` John W. Linville [this message]
2008-10-06 22:54 ` 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=20081006213909.GN3448@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dcbw@redhat.com \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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 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).