LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "roland" <devzero@web.de>
To: "Oliver Neukum" <oneukum@suse.de>
Cc: <linux-kernel@vger.kernel.org>, <bunk@stusta.de>
Subject: Re: [RFC] - Schedule mcdx for removal ? was: warning: #warning You have not edited mcdx.h
Date: Fri, 23 Mar 2007 23:59:40 +0100 [thread overview]
Message-ID: <06e401c76d9e$f0920430$eeeea8c0@aldipc> (raw)
In-Reply-To: <200703221035.19832.oneukum@suse.de>
why not?
why should unused code be maintained to death ?
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....
----- Original Message -----
From: "Oliver Neukum" <oneukum@suse.de>
To: "roland" <devzero@web.de>
Cc: <linux-kernel@vger.kernel.org>; <bunk@stusta.de>
Sent: Thursday, March 22, 2007 10:35 AM
Subject: Re: [RFC] - Schedule mcdx for removal ? was: warning: #warning You
have not edited mcdx.h
Am Donnerstag, 22. März 2007 10:14 schrieb roland:
> i wonder if there still exist any of those devices in functional state in
> this world, at least not attached to some system being able to boot
> 2.6.21+ - so, maybe mcdx driver is something for
> Documentation/feature-removal-schedule.txt , being removed in 2.6.25 or so
> after being announced for some time (i.e. driver telling "i will be gone
> soon, go spend those $15 to get a new drive") ?
Why? For the sake of sheer removal?
Regards
Oliver
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
This signature is a legal requirement
next prev parent reply other threads:[~2007-03-23 22:56 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 [this message]
2007-03-23 23:09 ` Adrian Bunk
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='06e401c76d9e$f0920430$eeeea8c0@aldipc' \
--to=devzero@web.de \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oneukum@suse.de \
--subject='Re: [RFC] - Schedule mcdx for removal ? was: warning: #warning You have not edited mcdx.h' \
/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
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).