mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Driver removals
Date: Sat, 16 Feb 2008 00:28:30 +0200	[thread overview]
Message-ID: <20080215222830.GA9962@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <47B5E2FD.9060908@tmr.com>

On Fri, Feb 15, 2008 at 02:07:41PM -0500, Bill Davidsen wrote:
> Adrian Bunk wrote:
>> On Wed, Feb 13, 2008 at 09:26:26PM -0500, Bill Davidsen wrote:
>>> ...
>>> In general, if a driver works and is being used, until it *needs*   
>>> attention I see no reason to replace it. I don't agree that "it 
>>> forces  people to try the new driver" is a valid reason, being 
>>> unmaintained is  only a problem if it needs maintenance. I am not 
>>> going to reopen that  topic, I'm simply noting a general opposition 
>>> to unfunded mandates, and  requiring changes to kernel, module and/or 
>>> rc.local config is just that.
>>
>> Keeping a working unmaintained driver in the tree is not a big deal - 
>> we have hundreds of them.
>>
>> But you miss the main point that removal of an obsolete driver with a  
>> new replacement driver forces people to finally report their problems  
>> with the new driver, thus making the new driver better.
>>
> You sure are proud of that new driver! People won't use it because the  
> old one is working fine, so you think it's fine to force them to make  
> changes in their system to use the new driver.

Sometimes what is best in the global picture is not what everyone
subjectively considers to be the best thing for him.

Well, our whole society is based on this principle...

> Best case is it works  
> after costing the user some time, worst case it doesn't and breaks their  
> system, so they stop upgrading the kernel and don't get security fixes.
>...

Instead of sending a bug report?

When removing an obsolete driver adult people suddenly start whining
"the new driver didn't work for me when I tried it one year ago".

And when asking where they reported the bug in the new driver the answer 
is that they didn't report it.

Driver development heavily relies on getting bug reports when something 
doesn't work.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-02-15 22:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  2:26 Bill Davidsen
2008-02-14  8:25 ` Adrian Bunk
2008-02-15 19:07   ` Bill Davidsen
2008-02-15 22:28     ` Adrian Bunk [this message]
2008-02-16  1:08       ` Bill Davidsen
2008-02-16  1:52         ` Valdis.Kletnieks
2008-02-16  7:39           ` Willy Tarreau
2008-02-17  4:27             ` Valdis.Kletnieks
2008-02-16 18:11           ` Bill Davidsen
2008-02-16  7:19         ` Adrian Bunk
2008-02-16 10:52           ` David Newall

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=20080215222830.GA9962@cs181133002.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®