linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Thorsten Leemhuis" <fedora@leemhuis.info>,
	"Greg KH" <greg@kroah.com>,
	rt2400-devel@lists.sourceforge.net,
	linux-wireless@vger.kernel.org
Subject: Re: rtl2860 driver in mainline?
Date: Tue, 28 Oct 2008 01:02:26 -0700	[thread overview]
Message-ID: <43e72e890810280102i3df34e2h9bf281c5d1e00a48@mail.gmail.com> (raw)
In-Reply-To: <1225180598.3796.66.camel@johannes.berg>

On Tue, Oct 28, 2008 at 12:56 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Tue, 2008-10-28 at 08:03 +0100, Thorsten Leemhuis 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.
>
> I don't think it makes sense either, at _best_ it'll do nothing but help
> a few users [1], and if somebody actually starts working on the vendor
> driver because it's in staging that's actively harmful to the real
> driver by diverting resources away from it.
>
> johannes
>
> [1] I used to think the point wasn't to make users happy but to make it
> easier to work on those drivers, but that objective seems long gone

Problem is distributions already ship crap anyway.

  Luis

  reply	other threads:[~2008-10-28  8:02 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
2008-10-28  7:56   ` Johannes Berg
2008-10-28  8:02     ` Luis R. Rodriguez [this message]
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=43e72e890810280102i3df34e2h9bf281c5d1e00a48@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=fedora@leemhuis.info \
    --cc=greg@kroah.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --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 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).