From: Nathaniel <nwf@cinci.rr.com>
To: Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.31
Date: Sun, 11 Aug 2002 01:18:27 -0400 [thread overview]
Message-ID: <3D55F3A3.8080607@cinci.rr.com> (raw)
In-Reply-To: Pine.LNX.4.33.0208101854340.2656-100000@penguin.transmeta.com
> Linus Torvalds <torvalds@home.transmeta.com>:
> o Fix up problem with Alan's pnpbios fixes for per-cpu GDT'
gcc -Wp,-MD,./.pnpbios_core.o.d -D__KERNEL__ -I/home/nwf/src/kernel/linux-2.5.31/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 -nostdinc -iwithprefix include -DKBUILD_BASENAME=pnpbios_core -DEXPORT_SYMTAB -c -o pnpbios_core.o pnpbios_core.c
pnpbios_core.c: In function `call_pnp_bios':
pnpbios_core.c:166: invalid lvalue in unary `&'
pnpbios_core.c:166: invalid lvalue in unary `&'
pnpbios_core.c:168: invalid lvalue in unary `&'
pnpbios_core.c:168: invalid lvalue in unary `&'
pnpbios_core.c: In function `pnpbios_init':
pnpbios_core.c:1275: invalid lvalue in unary `&'
pnpbios_core.c:1275: invalid lvalue in unary `&'
pnpbios_core.c:1276: invalid lvalue in unary `&'
pnpbios_core.c:1276: invalid lvalue in unary `&'
pnpbios_core.c:1277: invalid lvalue in unary `&'
pnpbios_core.c:1277: invalid lvalue in unary `&'
This patch allows it to compile (have not yet tested booting):
--- drivers/pnp/pnpbios_core.c.orig-nwf Sun Aug 11 01:11:40 2002
+++ drivers/pnp/pnpbios_core.c Sun Aug 11 01:11:54 2002
@@ -126,11 +126,11 @@
#define Q_SET_SEL(cpu, selname, address, size) \
set_base(cpu_gdt_table[cpu][(selname) >> 3], __va((u32)(address))); \
-set_limit(&cpu_gdt_table[cpu][(selname) >> 3], size)
+set_limit(cpu_gdt_table[cpu][(selname) >> 3], size)
#define Q2_SET_SEL(cpu, selname, address, size) \
set_base(cpu_gdt_table[cpu][(selname) >> 3], (u32)(address)); \
-set_limit(&cpu_gdt_table[cpu][(selname) >> 3], size)
+set_limit(cpu_gdt_table[cpu][(selname) >> 3], size)
/*
* At some point we want to use this stack frame pointer to unwind
--Nathan
next prev parent reply other threads:[~2002-08-11 5:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 2:04 Linux 2.5.31 Linus Torvalds
2002-08-11 5:18 ` Nathaniel [this message]
2002-08-11 5:22 ` Nathaniel
2002-08-11 11:44 ` Adrian Bunk
2002-08-11 13:59 ` Arnaldo Carvalho de Melo
2002-08-13 14:09 ` ecoffey
-- strict thread matches above, loose matches on Subject: below --
2002-08-11 19:21 Douglas Gilbert
[not found] <200208100551.46142.ivangurdiev@attbi.com.suse.lists.linux.kernel>
2002-08-11 10:16 ` Andi Kleen
2002-08-11 10:34 ` Russell King
2002-08-12 9:59 ` Helge Hafting
[not found] ` <mailman.1029062221.5995.linux-kernel2news@redhat.com>
2002-08-12 15:57 ` Pete Zaitcev
2002-08-10 9:51 Ivan Gyurdiev
2002-08-22 19:32 ` James Simmons
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=3D55F3A3.8080607@cinci.rr.com \
--to=nwf@cinci.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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