From: Greg KH <greg@kroah.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Ivo van Doorn <ivdoorn@gmail.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Luis Correia <luis.f.correia@gmail.com>,
Mike Galbraith <efault@gmx.de>,
linux-wireless@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today
Date: Thu, 30 Jul 2009 11:13:17 -0700 [thread overview]
Message-ID: <20090730181317.GA27543@kroah.com> (raw)
In-Reply-To: <1248977083.24886.4.camel@localhost.localdomain>
On Thu, Jul 30, 2009 at 02:04:43PM -0400, Dan Williams wrote:
> On Thu, 2009-07-30 at 10:26 -0700, Greg KH wrote:
> > On Thu, Jul 30, 2009 at 07:11:02PM +0200, Johannes Berg wrote:
> > > On Thu, 2009-07-30 at 18:52 +0200, Ivo van Doorn wrote:
> > >
> > > > [some text expressing his frustration]
> > >
> > > This is exactly why I was against staging all the time. Now suddenly
> > > "The Crap" seems like a viable alternative. WAKE UP PEOPLE. The code is
> > > not useful. Just look at the code that Mike pasted into his email. That
> > > alone should be enough to send cold shivers down your spine!
> >
> > Hm, "useful" is in the eye of the beholder.
> >
> > There is no driver in the mainline kernel tree for this device, so a
> > "normal" user has no chance of getting it working, right? That's why
> > -staging is working, there is a semi-working driver, and most
> > importantly, people willing to help out getting it working better.
> >
> > The combination of the two is what works here.
> >
> > So please, I understand your frustration on a lack of people helping out
> > with out-of-tree wireless drivers that don't quite work properly, but
> > please, that has NOTHING to do with the staging drivers.
> >
> > Meanwhile, I'm off on the driver-devel list helping Mike fix this
> > problem, which seems simple enough to solve...
>
> Except that the energy you're now investing in fixing this could have
> gone into rt2x00, and we would come out ahead in the end. Instead, the
> energy is sapped away by something that will *never* be mainlined.
On the contrary, I would have never spent any time working on rt2x00 :)
And are you trying to tell people _what_ to work on here? That's a
slippery slope...
thanks,
greg k-h
next prev parent reply other threads:[~2009-07-30 18:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 9:22 [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today Mike Galbraith
2009-07-30 9:29 ` Johannes Berg
2009-07-30 9:44 ` Mike Galbraith
2009-07-30 9:55 ` Johannes Berg
2009-07-30 10:05 ` Mike Galbraith
2009-07-30 12:11 ` [rt2800 doesn't authenticate (wpapsk/tkip)] " Mike Galbraith
2009-08-01 5:25 ` rt2800usb: memory corruption? Mike Galbraith
2009-08-01 10:55 ` Mike Galbraith
2009-08-02 0:21 ` Pavel Roskin
2009-08-02 5:16 ` Mike Galbraith
2009-08-02 6:29 ` Mike Galbraith
2009-08-02 6:47 ` Mike Galbraith
2009-08-06 10:12 ` Pavel Roskin
2009-07-30 10:06 ` [wireless] rt2870sta BUGs on shutdown, 2.6.30.2->git.today+git.wireless.today Luis Correia
2009-07-30 13:17 ` Bartlomiej Zolnierkiewicz
2009-07-30 16:52 ` Ivo van Doorn
2009-07-30 17:09 ` Mike Galbraith
2009-07-30 17:11 ` Johannes Berg
2009-07-30 17:26 ` Greg KH
2009-07-30 18:04 ` Dan Williams
2009-07-30 18:13 ` Greg KH [this message]
2009-08-02 9:10 ` Peter Teoh
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=20090730181317.GA27543@kroah.com \
--to=greg@kroah.com \
--cc=bzolnier@gmail.com \
--cc=dcbw@redhat.com \
--cc=efault@gmx.de \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=luis.f.correia@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).