From: Dan Aizenstros <dan@quicklogic.com>
To: linux-mips@oss.sgi.com
Subject: Changes to arch/mips/kernel/setup.c
Date: Thu, 06 Sep 2001 16:36:24 -0400 [thread overview]
Message-ID: <3B97DE48.10507@quicklogic.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
Hello All,
The latest changes to the setup.c file does not work correctly and
cause a compile failure. I have attached a patch which fixes it.
Dan Aizenstros
QuickLogic Canada
[-- Attachment #2: setup.c.diff --]
[-- Type: text/plain, Size: 602 bytes --]
Index: setup.c
===================================================================
RCS file: /cvs/linux/arch/mips/kernel/setup.c,v
retrieving revision 1.70
diff -u -r1.70 setup.c
--- setup.c 2001/09/06 02:42:30 1.70
+++ setup.c 2001/09/06 20:32:43
@@ -367,12 +367,12 @@
mips_cpu.options |= MIPS_CPU_FPU;
mips_cpu.scache.flags = MIPS_CACHE_NOT_PRESENT;
break;
-#endif /* CONFIG_CPU_MIPS32 */
default:
mips_cpu.cputype = CPU_UNKNOWN;
break;
}
break;
+#endif /* CONFIG_CPU_MIPS32 */
case PRID_COMP_SIBYTE:
switch (mips_cpu.processor_id & 0xff00) {
case PRID_IMP_SB1:
reply other threads:[~2001-09-06 20:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B97DE48.10507@quicklogic.com \
--to=dan@quicklogic.com \
--cc=linux-mips@oss.sgi.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