From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.13-pre1: sonypi.c compile error
Date: Fri, 12 Oct 2001 10:34:33 +0200 [thread overview]
Message-ID: <20011012103433.A2137@come.alcove-fr> (raw)
In-Reply-To: <3BC62542.CDEAAE@eyal.emu.id.au>
In-Reply-To: <3BC62542.CDEAAE@eyal.emu.id.au>
On Fri, Oct 12, 2001 at 09:03:30AM +1000, Eyal Lebedinsky wrote:
> gcc -D__KERNEL__ -I/data2/usr/local/src/linux-2.4-pre/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> -march=i686 -malign-functions=4 -DMODULE -DMODVERSIONS -include
> /data2/usr/local/src/linux-2.4-pre/include/linux/modversions.h
> -DEXPORT_SYMTAB -c sonypi.c
> sonypi.c: In function `sonypi_init_module':
> sonypi.c:702: `is_sony_vaio_laptop_R7462d5e4' undeclared (first use in
> this function)
Just add a
extern int is_sony_vaio_laptop; /* set in DMI table parse routines */
line somewhere at the beginning of the file drivers/char/sonypi.c
Looks like the driver sync between Linus and Alan was incomplete
this time (Linus took the sonypi driver changes but not the dmi_scan
routine changes).
I won't submit a patch to Linus for now, I'm pretty sure that
Alan will take care of this for -pre2.
Stelian.
--
Stelian Pop <stelian.pop@fr.alcove.com>
|---------------- Free Software Engineer -----------------|
| Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 |
|------------- Alcôve, liberating software ---------------|
next prev parent reply other threads:[~2001-10-12 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 23:03 Eyal Lebedinsky
2001-10-12 7:50 ` Alan Cox
2001-10-12 8:34 ` Stelian Pop [this message]
2001-10-12 11:08 ` Eyal Lebedinsky
2001-10-15 16:08 Sander van Geloven
2001-10-15 10:55 ` Peter T. Breuer
2001-10-15 11:18 ` Federico Sevilla III
2001-10-15 11:46 ` Stelian Pop
2001-10-15 11:58 ` 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=20011012103433.A2137@come.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=eyal@eyal.emu.id.au \
--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®