Re: disable_ide_dma gcc-3.0 warn

From: Ingo Oeser (ingo.oeser@informatik.tu-chemnitz.de)
Date: Mon Apr 23 2001 - 04:38:41 EST

Next message: alad@hss.hns.com: "xtime.tv_usec update in timer interrupt"
Previous message: Alan Cox: "Re: Kernel hang on multi-threaded X process crash"
In reply to: J . A . Magallon: "disable_ide_dma gcc-3.0 warn"
Next in thread: Alan Cox: "Re: disable_ide_dma gcc-3.0 warn"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, Apr 23, 2001 at 11:07:53AM +0200, J . A . Magallon wrote:
> In dmi_scan.c there is the func:
> static __init int disable_ide_dma(struct dmi_blacklist *d)
>
> But now it is unused (intentionally ?):
>
> static __initdata struct dmi_blacklist dmi_blacklist[]={
> #if 0 <==================
> { disable_ide_dma, "KT7", { /* Overbroad right now - kill DMA on problem KT7
> boards */
> MATCH(DMI_PRODUCT_NAME, "KT7-RAID"),
> NO_MATCH, NO_MATCH, NO_MATCH
> } },
> #endif

I guess this is a leftover from the VIA buggy southbridge workaround hunt.

Code marked with "#if 0" and "#if 1" is usally under
development and subject to changes.

Or left intentionally in "#if 0" to show the reader that we had
an wrong idea once, which seemed to be obviously correct (may be
from the docs) and we solved it with a different method, which is
not obvious or even not stated in the docs, but is the right one.

So we avoid stupid patches by leaving such things for reference.

In short: Don't care about new dead code too much, if it will be
needed by a "#if 0" marked code section.

BTW: Which revision of gcc 3.0 do you use? I had no luck compiling
it yet. Please answer in private to gcc issues.

Regards

Ingo Oeser

-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<     been there and had much fun   >>>>>>>>>>>>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: alad@hss.hns.com: "xtime.tv_usec update in timer interrupt"
Previous message: Alan Cox: "Re: Kernel hang on multi-threaded X process crash"
In reply to: J . A . Magallon: "disable_ide_dma gcc-3.0 warn"
Next in thread: Alan Cox: "Re: disable_ide_dma gcc-3.0 warn"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Apr 23 2001 - 21:00:44 EST