From: Kevin Fenzi <kevin@scrye.com>
To: Zsolt Babak <zod@sch.bme.hu>
Cc: inux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc8-laptop1 released
Date: Fri, 13 Jun 2003 11:51:30 -0400 [thread overview]
Message-ID: <S265421AbTFMPva/20030613155130Z+2583@vger.kernel.org> (raw)
In-Reply-To: <20030613114324.GA24705@gandalf.sch.bme.hu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Zsolt" == Zsolt Babak <zod@sch.bme.hu> writes:
Zsolt> Hi! This has nothing to do with the laptop patch, these
Zsolt> defines are really missing from include/linux/pci_ids.h.
ah... so I see.
Zsolt> In -rc5 I just removed the line from the .c file that
Zsolt> referenced the missing ID, and it works very well...
Zsolt> Maybe this is a bug ;)
Yeah, looks like, or something that wasn't entirely merged.
Commenting those out gets me further, but then it fails in:
ld -m elf_i386 -r -o cpqphp.o cpqphp_core.o cpqphp_ctrl.o cpqphp_proc.o cpqphp_pci.o
gcc -D__KERNEL__ -I/usr/src/redhat/BUILD/kernel-2.4.21rc8laptop1/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=pentium4 -DMODULE -DMODVERSIONS -include /usr/src/redhat/BUILD/kernel-2.4.21rc8laptop1/include/linux/modversions.h -nostdinc -iwithprefix include -DKBUILD_BASENAME=acpiphp_core -c -o acpiphp_core.o acpiphp_core.c
gcc -D__KERNEL__ -I/usr/src/redhat/BUILD/kernel-2.4.21rc8laptop1/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=pentium4 -DMODULE -DMODVERSIONS -include /usr/src/redhat/BUILD/kernel-2.4.21rc8laptop1/include/linux/modversions.h -nostdinc -iwithprefix include -DKBUILD_BASENAME=acpiphp_glue -c -o acpiphp_glue.o acpiphp_glue.c
acpiphp_glue.c: In function `find_host_bridge':
acpiphp_glue.c:815: warning: passing arg 2 of `acpi_get_object_info_R4d2dc830' from incompatible pointer type
acpiphp_glue.c:821: subscripted value is neither array nor pointer
acpiphp_glue.c:826: incompatible type for argument 1 of `strcmp'
make[3]: *** [acpiphp_glue.o] Error 1
make[3]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.4.21rc8laptop1/drivers/hotplug'
make[2]: *** [_modsubdir_hotplug] Error 2
make[2]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.4.21rc8laptop1/drivers'
make[1]: *** [_mod_drivers] Error 2
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.4.21rc8laptop1'
error: Bad exit status from /var/tmp/rpm-tmp.58636 (%build)
Something related to the i830 stuff someone else reported problems
with?
Zsolt> Zod.
kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE+6fX43imCezTjY0ERAnJlAJ9mcRMTcbkzn/ZehaGJFzh7wp4o3wCfaIJX
BwSw91MAR7gzaNaqyGlvSEA=
=uMbl
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-13 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 20:39 2.4.21-rc8-laptop1 released Hanno Böck
2003-06-12 21:17 ` Kevin Fenzi
2003-06-13 11:43 ` Zsolt Babak
2003-06-13 15:51 ` Kevin Fenzi [this message]
2003-06-12 22:27 ` Disconnect
2003-06-13 1:13 Brad Chapman
2003-06-13 21:55 ` Dave Jones
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=S265421AbTFMPva/20030613155130Z+2583@vger.kernel.org \
--to=kevin@scrye.com \
--cc=inux-kernel@vger.kernel.org \
--cc=zod@sch.bme.hu \
/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).