From: Adrian Bunk <bunk@stusta.de>
To: roland <devzero@web.de>
Cc: Oliver Neukum <oneukum@suse.de>, linux-kernel@vger.kernel.org
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: <20070323230904.GY752@stusta.de> (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.
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
prev parent 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 [RFC] - Schedule mcdx for removal ? was: warning: #warning You have not edited mcdx.h 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:
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=20070323230904.GY752@stusta.de \
--to=bunk@stusta.de \
--cc=devzero@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oneukum@suse.de \
/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.