From: Xose Vazquez Perez <xose@wanadoo.es>
To: Tosatti <marcelo@conectiva.com.br>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.4.22-pre7 bugs
Date: Mon, 21 Jul 2003 20:00:36 +0200 [thread overview]
Message-ID: <3F1C2A44.7020504@wanadoo.es> (raw)
hi,
there is a bug at drivers/hotplug/acpiphp_glue.c :
--cut--
gcc -D__KERNEL__ -I/datos/kernel/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=athlon -DMODULE -DMODVERSIONS -include /datos/kernel/linux/include/linux/modversions.h -nostdinc -iwithprefix include -DKBUILD_BASENAME=acpiphp_glue -c -o acpiphp_glue.o acpiphp_glue.c
acpiphp_glue.c:1172: variable `acpi_pci_hp_driver' has initializer but incomplete type
acpiphp_glue.c:1173: unknown field `add' specified in initializer
acpiphp_glue.c:1173: warning: excess elements in struct initializer
acpiphp_glue.c:1173: warning: (near initialization for `acpi_pci_hp_driver')
acpiphp_glue.c:1174: unknown field `remove' specified in initializer
acpiphp_glue.c:1174: warning: excess elements in struct initializer
acpiphp_glue.c:1174: warning: (near initialization for `acpi_pci_hp_driver')
acpiphp_glue.c: In function `acpiphp_glue_init':
acpiphp_glue.c:1188: warning: implicit declaration of function `acpi_pci_register_driver'
/datos/kernel/linux/include/linux/ctype.h: At top level:
acpiphp_glue.c:1172: storage size of `acpi_pci_hp_driver' isn't known
make[2]: *** [acpiphp_glue.o] Error 1
make[2]: Leaving directory `/datos/kernel/linux/drivers/hotplug'
make[1]: *** [_modsubdir_hotplug] Error 2
make[1]: Leaving directory `/datos/kernel/linux/drivers'
make: *** [_mod_drivers] Error 2
--end--
and drivers/scsi/aic79xx is empty, delete it.
-thanks-
regards,
--
I don't even see the code. All I see is blonde, brunette, redhead.
reply other threads:[~2003-07-21 17:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F1C2A44.7020504@wanadoo.es \
--to=xose@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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;
as well as URLs for NNTP newsgroup(s).