From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: acpi-support@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc7 ACPI broken
Date: Wed, 4 Jun 2003 22:16:14 +0100 [thread overview]
Message-ID: <200306042216.19142@gjs> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A847E96F25@orsmsx401.jf.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I know that latest acpi patch is against -rc3, but it aply to -rc7 just with
one problem in documentation, so i dont care. Anyway, recompilation if it
fails:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.21-rc7/include -Wall -Wstrict-prototypes
- -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer
- -pipe -mpreferred-stack-boundary=2 -march=i686 -falign-functions=0
- -falign-jumps=0 -falign-loops=0 -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' from
incompatible pointer type
acpiphp_glue.c:821: error: subscripted value is neither array nor pointer
acpiphp_glue.c:826: error: incompatible type for argument 1 of `strcmp'
make[3]: *** [acpiphp_glue.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.21-rc7/drivers/hotplug'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.21-rc7/drivers/hotplug'
make[1]: *** [_subdir_hotplug] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.21-rc7/drivers'
make: *** [_dir_drivers] Error 2
Any chance to get quick fix of that ?
Please CC me, i am not subscribed to acpi mailing list.
Thanks
> > > Old ACPI code, get patch from http://sf.net/projects/acpi
> > and report back
> > > if problems persist.
> > Any chance to get patch against latest -rc7 ?
> It's big, and deemed too risky. We are shooting for 2.4.22-pre1.
> Did it work for you?
- --
Grzegorz Jaskiewicz
K4 Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+3mGiqu082fCQYIgRAsBBAJ991RPum0QFcwRVqI8d3KTZp2NI6QCfSjAT
0obQhDO93Od0EjTHArZjEB0=
=oJ9C
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-04 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 20:49 2.4.21-rc7 ACPI broken Grover, Andrew
2003-06-04 20:37 ` Grzegorz Jaskiewicz
2003-06-04 21:16 ` Grzegorz Jaskiewicz [this message]
2003-06-09 20:32 ` 2.4.22 timeline was " Marcelo Tosatti
2003-06-10 0:47 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-06-04 21:42 Grover, Andrew
2003-06-04 20:58 Grover, Andrew
2003-06-04 18:01 Grover, Andrew
2003-06-04 20:27 ` Grzegorz Jaskiewicz
2003-06-04 21:31 ` Alan Cox
2003-06-12 16:32 ` Martin MOKREJŠ
2003-06-12 16:42 ` iain d broadfoot
2003-06-12 17:54 ` Martin MOKREJŠ
2003-06-04 17:49 Martin MOKREJŠ
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=200306042216.19142@gjs \
--to=gj@pointblue.com.pl \
--cc=acpi-support@lists.sourceforge.net \
--cc=andrew.grover@intel.com \
--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