From: Keith Owens <kaos@ocs.com.au>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: willy@debian.org, linux-kernel@vger.kernel.org,
parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: [Linux-ia64] Announce: modutils 2.4.24 is available
Date: Sun, 23 Mar 2003 14:41:33 +1100 [thread overview]
Message-ID: <8942.1048390893@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 22 Mar 2003 22:37:43 CDT." <200303230337.h2N3bhAC026836@hiauly1.hia.nrc.ca>
On Sat, 22 Mar 2003 22:37:43 -0500 (EST),
"John David Anglin" <dave@hiauly1.hia.nrc.ca> wrote:
>> -#if defined(ARCH_ia64) || defined(ARCH_ppc64)
>> +#if defined(ARCH_ia64) || defined(ARCH_ppc64) || defined(ARCH_hppa64)
>> #define HAS_FUNCTION_DESCRIPTORS
>> #endif
>
>The 32-bit hppa port also has function descriptors.
They keep coming out of the woodwork :( Any more architectures using
function descriptors? Just add them to the list below.
Index: 24.3/include/util.h
--- 24.3/include/util.h Sun, 23 Mar 2003 13:34:28 +1100 kaos (modutils-2.4/51_util.h 1.4 644)
+++ 24.3(w)/include/util.h Sun, 23 Mar 2003 14:40:06 +1100 kaos (modutils-2.4/51_util.h 1.4 644)
@@ -96,7 +96,7 @@ void gzf_close(int fd);
#define SYMPREFIX "__insmod_";
extern const char symprefix[10]; /* Must be sizeof(SYMPREFIX), including nul */
-#if defined(ARCH_ia64) || defined(ARCH_ppc64)
+#if defined(ARCH_ia64) || defined(ARCH_ppc64) || defined(ARCH_hppa) || defined(ARCH_hppa64)
#define HAS_FUNCTION_DESCRIPTORS
#endif
prev parent reply other threads:[~2003-03-23 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 3:16 Keith Owens
2003-03-23 3:23 ` [Linux-ia64] " Matthew Wilcox
2003-03-23 3:29 ` Keith Owens
2003-03-23 3:37 ` [parisc-linux] " John David Anglin
2003-03-23 3:41 ` Keith Owens [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=8942.1048390893@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=parisc-linux@parisc-linux.org \
--cc=willy@debian.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
all inboxes | Powered by JetHome®