All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Driver removals
Date: Wed, 13 Feb 2008 21:26:26 -0500	[thread overview]
Message-ID: <fp08q7$jv0$1@ger.gmane.org> (raw)

Just a general thought on removing drivers in general, when a driver is 
removed because there's a better one, it would be good to have either a 
message which shows up at "make oldconfig" time, or a file listing the 
driver(s) which replace it.

Half the resistance to removing drivers is finding what is supposed to 
replace the driver. For instance a list of all the drivers Adrian Bunk 
has suggested to replace sk98lin, so users have something better than 
searching the source code and/or LKML archive to find the next thing to try.

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.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


             reply	other threads:[~2008-02-14  2:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  2:26 Bill Davidsen [this message]
2008-02-14  8:25 ` Driver removals Adrian Bunk
2008-02-15 19:07   ` Bill Davidsen
2008-02-15 22:28     ` Adrian Bunk
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='fp08q7$jv0$1@ger.gmane.org' \
    --to=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 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.