All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: disable_ide_dma gcc-3.0 warn
Date: Mon, 23 Apr 2001 11:07:53 +0200	[thread overview]
Message-ID: <20010423110753.A25081@werewolf.able.es> (raw)

Hi, everyone.

One other gcc-3.0 warning (apart from the classic multiline strings)
I do not know if it can be important.

gcc -D__KERNEL__ -I/usr/src/linux-2.4.3-ac12/include -Wall -Wstrict-prototypes -
O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 
-march=i686    -c -o dmi_scan.o dmi_scan.c
dmi_scan.c:158: warning: `disable_ide_dma' defined but not used

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  
    { broken_apm_power, "Dell Inspiron 5000e", {    /* Handle problems with APM
on Inspiron 5000e */
            MATCH(DMI_BIOS_VENDOR, "Phoenix Technologies LTD"),
            MATCH(DMI_BIOS_VERSION, "A04"),
            MATCH(DMI_BIOS_DATE, "08/24/2000"), NO_MATCH
            } },
    { NULL, }
};

-- 
J.A. Magallon                                          #  Let the source
mailto:jamagallon@able.es                              #  be with you, Luke... 

Linux werewolf 2.4.3-ac12 #1 SMP Sun Apr 22 10:27:22 CEST 2001 i686


             reply	other threads:[~2001-04-23  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23  9:07 J . A . Magallon [this message]
2001-04-23  9:38 ` disable_ide_dma gcc-3.0 warn Ingo Oeser
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=20010423110753.A25081@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.