From: Robert Love <rml@tech9.net>
To: Oliver Pitzeier <o.pitzeier@uptime.at>
Cc: axp-kernel-list@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH] Re: Kernel 2.5.8 on Alpha
Date: 15 Apr 2002 14:47:42 -0400 [thread overview]
Message-ID: <1018896466.857.12.camel@phantasy> (raw)
In-Reply-To: <000001c1e3f7$86214880$1201a8c0@pitzeier.priv.at>
On Sun, 2002-04-14 at 17:01, Oliver Pitzeier wrote:
> I tried to compile kernel 2.5.8 on an Alpha. I just wanted to try it...
> This happens:
> <snip>
> sched.c: In function `schedule':
> sched.c:771: `PREEMPT_ACTIVE' undeclared (first use in this function)
2.5.8-pre2 uses PREEMPT_ACTIVE directly in entry.S and thus moved the
definition of PREEMPT_ACTIVE into include/asm/thread_info.h from
include/linux/sched.h, presumably because including sched.h in entry.S
would not be pretty.
Each arch thus needs to define PREEMPT_ACTIVE ... patch applied.
Robert Love
diff -urN linux-2.5.8/include/asm-alpha/thread_info.h linux/include/asm-alpha/thread_info.h
--- linux-2.5.8/include/asm-alpha/thread_info.h Sun Apr 14 15:18:56 2002
+++ linux/include/asm-alpha/thread_info.h Mon Apr 15 14:32:50 2002
@@ -53,6 +53,8 @@
#endif /* __ASSEMBLY__ */
+#define PREEMPT_ACTIVE 0x4000000
+
/*
* Thread information flags:
* - these are process state flags and used from assembly
next prev parent reply other threads:[~2002-04-15 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3CB8B939.54A8E170@acsu.buffalo.edu>
2002-04-14 21:01 ` Kernel 2.5.8 on Alpha Oliver Pitzeier
2002-04-15 18:47 ` Robert Love [this message]
2002-04-16 14:43 ` [PATCH] " Ivan Kokshaysky
2002-04-30 15:36 ` Success Story: Kernel 2.5.11 on Alpha (AS1000) Oliver Pitzeier
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=1018896466.857.12.camel@phantasy \
--to=rml@tech9.net \
--cc=axp-kernel-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=o.pitzeier@uptime.at \
/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