From: Pavel Machek <pavel@ucw.cz>
To: "David S. Miller" <davem@redhat.com>
Cc: hch@infradead.org, arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: ioctl cleanups: enable sg_io and serial stuff to be shared
Date: Fri, 9 May 2003 01:03:38 +0200 [thread overview]
Message-ID: <20030508230337.GA139@elf.ucw.cz> (raw)
In-Reply-To: <20030508.134300.122085520.davem@redhat.com>
Hi!
> From: Pavel Machek <pavel@ucw.cz>
> Date: Thu, 8 May 2003 22:33:14 +0200
>
> What about this one: redefine it to (*ioctl)( ...., unsigned *long*,
> unsinged long). That means we can add
>
> #define IOCTL_COMPAT 0x1 0000 0000
>
> Bzzt! Doesn't work on 32-bit. COMPAT does not mean 64-bit-->32-bit
> translations, stop thinking about the compat layer in this way.
>
> It is a generic environment translation system.
>
> Eventually we can use it for things like IBCS2 and stuff like that.
I... do not think so.
You'd then need
.compat_linux32_ioctl
.compat_IBCS2_ioctl
...
I do not think that is doable.
> Suggest something sane like defining a macro such as
> "compat_task(tsk)" that can be tested by various bits of
> code.
That makes more sense. Unfortunately, that means that case "okay, it
is compatible" can not be told from "we did not bother to check
compat_task()". :-(. Nor do I see a transition phase.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-05-08 22:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030507104008$12ba@gated-at.bofh.it>
2003-05-07 11:51 ` ioctl cleanups: enable sg_io and serial stuff to be shared Arnd Bergmann
2003-05-07 12:41 ` Pavel Machek
2003-05-07 12:56 ` Christoph Hellwig
2003-05-07 14:39 ` David S. Miller
2003-05-07 15:12 ` Jeff Garzik
2003-05-07 14:07 ` David S. Miller
2003-05-08 10:46 ` Gerd Knorr
2003-05-08 15:16 ` Ben Collins
2003-05-08 15:51 ` Christoph Hellwig
2003-05-08 15:37 ` Ben Collins
2003-05-08 19:34 ` Pavel Machek
2003-05-08 19:27 ` Ben Collins
2003-05-08 20:06 ` Pavel Machek
2003-05-08 19:47 ` Ben Collins
2003-05-08 20:09 ` David S. Miller
2003-05-08 20:26 ` David Mosberger
2003-05-08 20:33 ` Arjan van de Ven
2003-05-08 21:11 ` David Mosberger
2003-05-08 15:23 ` Arnd Bergmann
2003-05-07 15:28 ` Pavel Machek
2003-05-07 16:04 ` David S. Miller
2003-05-07 19:13 ` Arnd Bergmann
2003-05-07 18:12 ` David S. Miller
2003-05-07 23:50 ` Arnd Bergmann
2003-05-08 10:35 ` David S. Miller
2003-05-07 22:20 ` Alan Cox
2003-05-08 20:33 ` Pavel Machek
2003-05-08 20:43 ` David S. Miller
2003-05-08 23:03 ` Pavel Machek [this message]
2003-05-08 23:35 ` Arnd Bergmann
2003-05-08 22:48 ` Arnd Bergmann
2003-05-08 23:22 ` Pavel Machek
2003-05-07 13:18 ` Arnd Bergmann
2003-05-07 14:01 ` Carl-Daniel Hailfinger
2003-05-07 15:16 ` Pavel Machek
2003-05-07 15:46 ` Arnd Bergmann
2003-05-07 16:07 ` Jens Axboe
2003-05-07 16:20 ` Arnd Bergmann
2003-05-07 10:27 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=20030508230337.GA139@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=arnd@arndb.de \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--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 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.