From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: disable_ide_dma gcc-3.0 warn
Date: Mon, 23 Apr 2001 11:38:41 +0200 [thread overview]
Message-ID: <20010423113841.Q682@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20010423110753.A25081@werewolf.able.es>
In-Reply-To: <20010423110753.A25081@werewolf.able.es>; from jamagallon@able.es on Mon, Apr 23, 2001 at 11:07:53AM +0200
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 >>>>>>>>>>>>
next prev parent reply other threads:[~2001-04-23 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 9:07 J . A . Magallon
2001-04-23 9:38 ` Ingo Oeser [this message]
2001-04-23 9:55 ` Alan Cox
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=20010423113841.Q682@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®