From: Jeff Chua <jeffchua@silk.corp.fedex.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: needed this to run 2.4.6-pre4
Date: Thu, 21 Jun 2001 21:31:01 +0800 (SGT) [thread overview]
Message-ID: <Pine.LNX.4.33.0106212128241.272-100000@boston.corp.fedex.com> (raw)
still not in 2.4.6-pre4. Without this, you'll get a lot of undefined
symbols referencing do_softirq
Jeff
[ jchua@fedex.com ]
--- include/asm-i386/softirq.h Thu Jun 14 17:10:34 2001
+++ include/asm-i386/softirq.h.new Thu Jun 14 17:17:15 2001
@@ -36,13 +36,13 @@
\
".section .text.lock,\"ax\";" \
"2: pushl %%eax; pushl %%ecx; pushl %%edx;" \
- "call do_softirq;" \
+ "call %c1;" \
"popl %%edx; popl %%ecx; popl %%eax;" \
"jmp 1b;" \
".previous;" \
\
: /* no output */ \
- : "r" (ptr) \
+ : "r" (ptr), "i" (do_softirq) \
/* no registers clobbered */ ); \
} while (0)
next reply other threads:[~2001-06-21 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 13:31 Jeff Chua [this message]
2001-06-21 17:13 ` needed this to run 2.4.6-pre4 Jeff Garzik
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=Pine.LNX.4.33.0106212128241.272-100000@boston.corp.fedex.com \
--to=jeffchua@silk.corp.fedex.com \
--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;
as well as URLs for NNTP newsgroup(s).