From: Andi Kleen <ak@muc.de>
To: mike.miller@hp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: cciss update for 2.6.7-rc1
Date: Fri, 04 Jun 2004 23:59:17 +0200 [thread overview]
Message-ID: <m3pt8ff0i2.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <23tkF-7Hg-29@gated-at.bofh.it> (mikem@beardog.cca.cpqcorp.net's message of "Fri, 04 Jun 2004 22:20:13 +0200")
mikem@beardog.cca.cpqcorp.net writes:
> @@ -451,6 +451,140 @@ static int cciss_release(struct inode *i
> return 0;
> }
>
> +#ifdef __x86_64__
> +/* for AMD 64 bit kernel compatibility with 32-bit userland ioctls */
> +#include <linux/syscalls.h>
> +extern int
> +register_ioctl32_conversion(unsigned int cmd, int (*handler)(unsigned int,
> + unsigned int, unsigned long, struct file *));
> +extern int unregister_ioctl32_conversion(unsigned int cmd);
This should be in CONFIG_COMPAT instead of testing for x86-64
and include <linux/compat.h> for the prototypes. linux/syscalls.h
should not be needed.
-Andi
next parent reply other threads:[~2004-06-04 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23tkF-7Hg-29@gated-at.bofh.it>
2004-06-04 21:59 ` Andi Kleen [this message]
2004-06-02 20:13 cciss update for 2.6.7-rc1 mikem
2004-06-04 20:42 ` Andrew Morton
2004-06-04 20:53 ` viro
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=m3pt8ff0i2.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.miller@hp.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