From: barryn@pobox.com (Barry K. Nathan)
To: mfedyk@matchmail.com (Mike Fedyk)
Cc: louisg00@bellsouth.net (Louis Garcia), linux-kernel@vger.kernel.org
Subject: [PATCH] Re: 2.4.15-pre4 compile error
Date: Mon, 12 Nov 2001 19:05:00 -0800 (PST) [thread overview]
Message-ID: <20011113030500.766F989A86@pobox.com> (raw)
In-Reply-To: <20011112173318.H32099@mikef-linux.matchmail.com> from "Mike Fedyk" at Nov 12, 2001 05:33:18 PM
> This patch, (from RML) will fix it.
>
> It's already been posted...
[snip]
FWIW, this is Linus' fix, turned into a patch...
-Barry K. Nathan <barryn@pobox.com>
diff -ruN linux-2.4.15-pre4/arch/i386/kernel/setup.c linux-2.4.15-pre4-bkn1/arch/i386/kernel/setup.c
--- linux-2.4.15-pre4/arch/i386/kernel/setup.c Mon Nov 12 12:39:56 2001
+++ linux-2.4.15-pre4-bkn1/arch/i386/kernel/setup.c Mon Nov 12 13:04:24 2001
@@ -2788,7 +2788,7 @@
static void *c_start(struct seq_file *m, loff_t *pos)
{
- return *pos < NR_CPUS ? &cpu_data[*pos] : NULL;
+ return *pos < NR_CPUS ? cpu_data+*pos : NULL;
}
static void *c_next(struct seq_file *m, void *v, loff_t *pos)
{
diff -ruN linux-2.4.15-pre4/include/asm-i386/processor.h linux-2.4.15-pre4-bkn1/include/asm-i386/processor.h
--- linux-2.4.15-pre4/include/asm-i386/processor.h Mon Nov 12 12:43:21 2001
+++ linux-2.4.15-pre4-bkn1/include/asm-i386/processor.h Mon Nov 12 13:33:01 2001
@@ -76,7 +76,7 @@
extern struct cpuinfo_x86 cpu_data[];
#define current_cpu_data cpu_data[smp_processor_id()]
#else
-#define cpu_data &boot_cpu_data
+#define cpu_data (&boot_cpu_data)
#define current_cpu_data boot_cpu_data
#endif
prev parent reply other threads:[~2001-11-13 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 1:27 2.4.15-pre4 compile error Louis Garcia
2001-11-13 1:33 ` Mike Fedyk
2001-11-13 3:05 ` Barry K. Nathan [this message]
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=20011113030500.766F989A86@pobox.com \
--to=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=louisg00@bellsouth.net \
--cc=mfedyk@matchmail.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