From: Greg KH <greg@kroah.com>
To: Luis Correia <luis.f.correia@gmail.com>
Cc: Thorsten Leemhuis <fedora@leemhuis.info>,
rt2400-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org
Subject: Re: rtl2860 driver in mainline?
Date: Tue, 28 Oct 2008 10:10:24 -0700 [thread overview]
Message-ID: <20081028171024.GC4818@kroah.com> (raw)
In-Reply-To: <efe7343f0810280048j57158020n67176d7a56f0bbea@mail.gmail.com>
On Tue, Oct 28, 2008 at 07:48:54AM +0000, Luis Correia wrote:
> Hi!
>
> On Tue, Oct 28, 2008 at 07:03, Thorsten Leemhuis <fedora@leemhuis.info> wrote:
> > On 28.10.2008 01:49, Greg KH wrote:
> >>
> >> So, on my quest to suck up every out-of-tree driver and get it into the
> >> main kernel tree (drivers/staging/ to start with), I've been pointed at
> >> the rtl2860 driver.
> >
> > Does it really make sense to include a driver when a different one for
> > mainline inclusion is being actively developed? It might give some
> > developers the impression that it's worth spending time improving the
> > rtl2860/2870 drivers -- which might be wasted time in the end.
>
> Is it just me or you are suggesting we use the Ralink supplied driver,
> with its own wireless stack, rather then work with the rt2x00 team?
No, See my other post in this thread about what I am suggesting.
> Do we really want that again (several wireless stacks)?
We already have that in the "crap" tree today (see drivers/staging/) :)
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-28 18:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 0:49 rtl2860 driver in mainline? Greg KH
2008-10-28 5:48 ` Ivo Van Doorn
2008-10-28 6:10 ` Greg KH
2008-10-28 6:23 ` Ivo Van Doorn
2008-10-28 14:59 ` Dan Williams
2008-10-28 17:24 ` Luis R. Rodriguez
2008-10-28 7:03 ` Thorsten Leemhuis
2008-10-28 7:48 ` Luis Correia
2008-10-28 8:01 ` Luis R. Rodriguez
2008-10-28 8:06 ` Thorsten Leemhuis
2008-10-28 17:10 ` Greg KH [this message]
2008-10-28 7:56 ` Johannes Berg
2008-10-28 8:02 ` Luis R. Rodriguez
2008-10-28 8:06 ` Luis Correia
2008-10-28 17:09 ` Greg KH
2008-10-28 8:12 ` Johannes Berg
2008-10-28 8:17 ` Luis R. Rodriguez
2008-10-28 8:19 ` Johannes Berg
2008-10-28 17:08 ` Greg KH
2008-10-28 18:35 ` Johannes Berg
2008-10-28 22:45 ` Greg KH
2008-10-29 10:13 ` Dan Williams
2008-10-29 16:30 ` Greg KH
2008-10-30 4:02 ` Dan Williams
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=20081028171024.GC4818@kroah.com \
--to=greg@kroah.com \
--cc=fedora@leemhuis.info \
--cc=linux-wireless@vger.kernel.org \
--cc=luis.f.correia@gmail.com \
--cc=rt2400-devel@lists.sourceforge.net \
/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.