linux-kernel - [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-next>] [day] [month] [year] [list]

Date:	Thu, 22 Mar 2007 10:14:18 +0100
From:	"roland" <devzero@....de>
To:	<linux-kernel@...r.kernel.org>
Cc:	<bunk@...sta.de>
Subject: [RFC] - Schedule mcdx for removal ? was:  warning: #warning You have not edited mcdx.h

anyway - i wonder if anybody is ever using 2.6.21+ on a system with one of 
those legacy mitsumi single-speed (LU-005/FX-001) and double-speed (FX-001D) 
cd-rom drives !?

iirc, these where the first drives available on the market (must have been 
around '94) and those were no ide/atapi compatible drives which had their 
own isa-bus controller.

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") ?

not 100% sure here, but there really may be nobody to complain about 
removing this one.....

regards
roland

ps:
hey, i just read discussions about removing RAW driver, so if THAT being 
discussed for removal, this one probably should have been removed already ! 
;)

----- Original Message ----- 
From: "roland" <devzero@....de>
To: <linux-kernel@...r.kernel.org>
Cc: <bunk@...sta.de>
Sent: Thursday, March 22, 2007 1:43 AM
Subject: 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: warning: #warning Perhaps irq and i/o settings 
> are wrong.
>
> looking into the code :
>
> #ifndef I_WAS_HERE
> #ifndef MODULE
> #warning You have not edited mcdx.h
> #warning Perhaps irq and i/o settings are wrong.
> #endif
> #endif
>
> and before:
> /* *** make the following line uncommented, if you're sure,
> * *** all configuration is done */
> /* #define I_WAS_HERE */
>
> huh?
>
> is this file meant to be edited before compile ?
>
>
> searched the list and came across some patch from adrian bunk:
>
> [Patch] (new version) configure mcdx without editing mcdx.h
>
> at http://marc.info/?l=linux-kernel&m=94772887906874&w=2
> and http://marc.info/?l=linux-kernel&m=94724271712637&w=2
> and http://marc.info/?l=linux-kernel&m=94699770112439&w=2
>
> has this never been merged ?
>
> regards
> roland
>
>
> 

-
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/