LKML Archive on
help / color / mirror / Atom feed
From: Adrian Bunk <>
To: roland <>
Cc: Oliver Neukum <>,
Subject: Re: [RFC] - Schedule mcdx for removal ? was:  warning: #warning You have not edited mcdx.h
Date: Sat, 24 Mar 2007 00:09:04 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <06e401c76d9e$f0920430$eeeea8c0@aldipc>

On Fri, Mar 23, 2007 at 11:59:40PM +0100, roland wrote:
> why not?
> why should unused code be maintained to death ?

This driver hasn't been actively maintained for years - it's nearly 
zero-cost to carry such a driver in the kernel sources.

> if there are discussions about removing features people are still using, i 
> think it should be legitimate to discuss about removing drivers nobody 
> needs anymore....

There's a difference between obsolete features and drivers for old 
hardware: There's usually a replacement for the obsolete features.



       "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:[~2007-03-23 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  9:14 roland
2007-03-22  9:35 ` Oliver Neukum
2007-03-23 22:59   ` roland
2007-03-23 23:09     ` Adrian Bunk [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [RFC] - Schedule mcdx for removal ? was:  warning: #warning You have not edited mcdx.h' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).