From: Andrew Morton <akpm@osdl.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: manfred@colorfullife.com, linux-arch@vger.kernel.org
Subject: Re: posix message queues
Date: Thu, 8 Apr 2004 01:49:31 -0700 [thread overview]
Message-ID: <20040408014931.5d56901f.akpm@osdl.org> (raw)
In-Reply-To: <200404081017.46132.arnd@arndb.de>
Arnd Bergmann <arnd@arndb.de> wrote:
>
> > No. The unix spec mandates 'long' for the final C-library api. Using u32
> > would mean that glibc would have to add an emulation layer in user space
> > for 64-bit archs. In the long run, 64-bit kernels running 64-bit apps
> > will be the common case. I don't want to add an emulation layer to the
> > common case.
>
> Coincidentally, I have just finished writing handlers for them.
In file included from kernel/sys.c:8:
include/linux/compat.h:98: error: `SIGEV_PAD_SIZE' undeclared here (not in a function)
---
25-akpm/include/linux/compat.h | 1 +
1 files changed, 1 insertion(+)
diff -puN include/linux/compat.h~compat_mq-fix include/linux/compat.h
--- 25/include/linux/compat.h~compat_mq-fix 2004-04-08 01:49:19.539180328 -0700
+++ 25-akpm/include/linux/compat.h 2004-04-08 01:49:19.541180024 -0700
@@ -13,6 +13,7 @@
#include <linux/sem.h>
#include <asm/compat.h>
+#include <asm/siginfo.h>
#define compat_jiffies_to_clock_t(x) \
(((unsigned long)(x) * COMPAT_USER_HZ) / HZ)
_
next prev parent reply other threads:[~2004-04-08 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 19:07 posix message queues Andrew Morton
2004-04-07 19:15 ` Manfred Spraul
2004-04-08 8:17 ` Arnd Bergmann
2004-04-08 8:49 ` Andrew Morton [this message]
2004-04-08 14:08 ` Manfred Spraul
2004-04-08 20:24 ` Andrew Morton
2004-04-09 23:45 ` David S. Miller
2004-04-10 11:19 ` Manfred Spraul
2004-04-10 11:53 ` Manfred Spraul
2004-04-10 20:43 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2004-04-08 22:22 Arnd Bergmann
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=20040408014931.5d56901f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=manfred@colorfullife.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