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 p
AIL PROTECTED]>
To: "roland" <[EMAIL PROTECTED]>
Cc: ; <[EMAIL PROTECTED]>
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 wo
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 , b
warning: #warning You have not edited mcdx.h
while looking at some more warnings i got with allyesconfig i came across
this really weird one:
In file included from drivers/cdrom/mcdx.c:78:
drivers/cdrom/mcdx.h:180:2: warning: #warning You have not edited mcdx.h
drivers/cdrom/mcdx.h:181:2:
while looking at some more warnings i got with allyesconfig i came across
this really weird one:
In file included from drivers/cdrom/mcdx.c:78:
drivers/cdrom/mcdx.h:180:2: warning: #warning You have not edited mcdx.h
drivers/cdrom/mcdx.h:181:2: warning: #warning Perhaps irq and i/o settings
5 matches
Mail list logo
