From: Ben Collins <bcollins@debian.org>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
schwidefsky@de.ibm.com, ak@suse.de, davem@redhat.com,
arnd@bergmann-dalldorf.de
Subject: Re: ioctl32 consolidation -- call for testing
Date: Thu, 27 Feb 2003 14:44:40 -0500 [thread overview]
Message-ID: <20030227194440.GM21100@phunnypharm.org> (raw)
In-Reply-To: <20030226222606.GA9144@elf.ucw.cz>
On Wed, Feb 26, 2003 at 11:26:06PM +0100, Pavel Machek wrote:
> Hi!
>
> This is next version of ioctl32 consolidation. At one point it
> compiled on x86-64 and sparc64. I'm not 100% sure it still does...
>
> Could you try to apply it on your architecture, fix whatever breakage
> it causes, and submit patch back to me?
>
> ia64 has very different ioctl32 emulation (and very short). What is
> going on there? Also not all architectures knew about
> register_ioctl32_translation. Ouch.
FYI, whatever changes you made to sparc64's ioctl32.c broke. Doesn't
appear that any of the 32bit ioctl's are registered, so the system never
boots to usermode fully (since it's completely 32bit).
Not sure I'll be able to look into the reason, but it's probably simple.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2003-02-27 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 22:26 ioctl32 consolidation -- call for testing Pavel Machek
2003-02-27 19:44 ` Ben Collins [this message]
2003-02-27 19:51 ` Ben Collins
2003-02-27 20:27 ` Ben Collins
2003-02-27 20:13 ` David S. Miller
2003-02-27 20:34 ` Ben Collins
2003-02-27 20:21 ` David S. Miller
2003-02-27 20:50 ` Ben Collins
2003-02-27 20:37 ` David S. Miller
2003-02-27 21:12 ` Ben Collins
2003-02-28 13:23 ` Pavel Machek
2003-02-28 15:49 ` Ben Collins
2003-03-01 0:52 ` David S. Miller
2003-02-28 13:20 ` 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=20030227194440.GM21100@phunnypharm.org \
--to=bcollins@debian.org \
--cc=ak@suse.de \
--cc=arnd@bergmann-dalldorf.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=schwidefsky@de.ibm.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 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.