linux-kernel - Re: [RFC] - Schedule mcdx for removal ? was: warning: #warning You have not edited mcdx.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 23 Mar 2007 23:59:40 +0100
From:	"roland" <devzero@....de>
To:	"Oliver Neukum" <oneukum@...e.de>
Cc:	<linux-kernel@...r.kernel.org>, <bunk@...sta.de>
Subject: Re: [RFC] - Schedule mcdx for removal ? was:  warning: #warning You have not edited mcdx.h

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@...e.de>
To: "roland" <devzero@....de>
Cc: <linux-kernel@...r.kernel.org>; <bunk@...sta.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 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/