From: Manfred Spraul <manfred@colorfullife.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Krzysztof Benedyczak <golbi@mat.uni.torun.pl>,
linux-kernel@vger.kernel.org,
Michal Wronski <wrona@mat.uni.torun.pl>
Subject: Re: [RFC][PATCH] 2/6 POSIX message queues
Date: Thu, 19 Feb 2004 20:44:17 +0100 [thread overview]
Message-ID: <40351211.1030200@colorfullife.com> (raw)
In-Reply-To: <20040219190720.GA2421@mars.ravnborg.org>
Sam Ravnborg wrote:
>Maybe something like:
>mqueue.h for kernel-only
>mqueue_abi.h for kernel+user
>
>
I don't think that this is necessary. Everything in <linux/> is kernel
only. user space should copy the headers and remove the kernel only
parts. kernel+user files mean that it's not possible rename structures
or move them around. Perhaps someone wants to move all 16-bit uid
structures into a <linux/compat/> directly - shared headers make that
impossible.
I agree that the placement of the #ifdef is a bit arbitrary - it's a
hint that the structures outside are visible to user space and must
remain unchanged.
Christoph: I'm sure there will be users that must call the message queue
functions directly from C code. E.g. the 32-bit emulation layers on
64/32 bit archs. And they need the prototypes.
--
Manfred
next prev parent reply other threads:[~2004-02-19 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 14:28 [RFC][PATCH] 2/6 POSIX message queues Krzysztof Benedyczak
2004-02-19 14:53 ` Christoph Hellwig
2004-02-19 19:07 ` Sam Ravnborg
2004-02-19 19:44 ` Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 13:55 Arnd Bergmann
2004-02-20 18:11 ` Krzysztof Benedyczak
2004-02-22 12:23 ` Arnd Bergmann
2004-02-22 15:12 Manfred Spraul
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=40351211.1030200@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=golbi@mat.uni.torun.pl \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=wrona@mat.uni.torun.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.