From: "David S. Miller" <davem@redhat.com>
To: pavel@suse.cz
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com, ak@suse.de
Subject: Re: share COMPATIBLE_IOCTL()s across architectures
Date: Wed, 19 Mar 2003 16:01:30 -0800 (PST) [thread overview]
Message-ID: <20030319.160130.112180221.davem@redhat.com> (raw)
In-Reply-To: <20030319232157.GA13415@elf.ucw.cz>
From: Pavel Machek <pavel@suse.cz>
Date: Thu, 20 Mar 2003 00:21:57 +0100
This patche moves common COMPATIBLE_IOCTLs to
include/linux/compat_ioctl.h, enabling pretty nice cleanups:
Please be careful. For anything non-trivial there can be major
differences between compat layers.
I say this now because eventually I want this compat stuff
to support multiple-compilations, using some COMPAT_NAME(foo)
macro scheme and some Makefile hackery.
This would allow, for example, x86_64 to have an x86_32 and
x86_32_sysv compat layer in one build. So for example in this case
fs/compat.c would be built twice, once with x86_32 compat types
and once with x86_32_sysv types.
next prev parent reply other threads:[~2003-03-19 23:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 23:21 share COMPATIBLE_IOCTL()s across architectures Pavel Machek
2003-03-20 0:01 ` David S. Miller [this message]
2003-03-20 19:32 ` Pavel Machek
2003-03-20 20:24 ` Andi Kleen
2003-03-21 10:21 ` Pavel Machek
[not found] <20030319232157.GA13415@elf.ucw.cz.suse.lists.linux.kernel>
2003-03-20 0:08 ` Andi Kleen
2003-03-20 19:33 ` Pavel Machek
2003-03-20 20:26 ` Andi Kleen
2003-03-21 10:24 ` Pavel Machek
[not found] <20030320001013$67af@gated-at.bofh.it>
[not found] ` <20030320001013$68b4@gated-at.bofh.it>
2003-03-20 1:35 ` Arnd Bergmann
2003-03-20 2:38 ` Andi Kleen
2003-03-20 10:30 ` Arnd Bergmann
2003-03-20 19:35 ` Pavel Machek
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=20030319.160130.112180221.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.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