From: "David S. Miller" <davem@redhat.com>
To: pavel@ucw.cz
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: sys32_ioctl -> compat_ioctl -- sparc64
Date: Tue, 04 Mar 2003 03:09:10 -0800 (PST) [thread overview]
Message-ID: <20030304.030910.63662193.davem@redhat.com> (raw)
In-Reply-To: <20030303232513.GA24047@elf.ucw.cz>
From: Pavel Machek <pavel@ucw.cz>
Date: Tue, 4 Mar 2003 00:25:13 +0100
This is sparc64-specific part. It removes hack where pointers to
functions were stored in 32bits, making ioctl table bigger, but I
guess that should not be a big problem (and can be fixed later).
This is OK temporarily, but should be fixed eventually.
prev parent reply other threads:[~2003-03-04 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 23:25 sys32_ioctl -> compat_ioctl -- sparc64 Pavel Machek
2003-03-04 11:09 ` David S. Miller [this message]
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=20030304.030910.63662193.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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;
as well as URLs for NNTP newsgroup(s).