From: Daniel Jacobowitz <dan@debian.org>
To: Greg KH <greg@kroah.com>
Cc: Valdis.Kletnieks@vt.edu, Dave Airlie <airlied@linux.ie>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.sourceforge.net
Subject: Re: From Eric Anholt:
Date: Tue, 11 May 2004 20:07:09 -0400 [thread overview]
Message-ID: <20040512000709.GA10233@nevyn.them.org> (raw)
In-Reply-To: <20040511234329.GA27242@kroah.com>
On Tue, May 11, 2004 at 04:43:29PM -0700, Greg KH wrote:
> On Tue, May 11, 2004 at 07:34:39PM -0400, Valdis.Kletnieks@vt.edu wrote:
> > On Wed, 12 May 2004 00:20:51 BST, Dave Airlie said:
> >
> > > I just looked at drm.h and nearly all the ioctls use int, this file is
> > > included in user-space applications also at the moment, I'm worried
> > > changing all ints to __u32 will break some of these, anyone on DRI list
> > > care to comment?
> >
> > Is this a case where somebody is *really* including kernel headers in userspace
> > and we need to smack them, or are they using a copy that's been sanitized
> > (and possibly fixed)?
>
> Don't know, but how are you dealing with the issue that an "int" is
> different for different kernel sizes (64 vs 32) and userspace too.
> That's why you can't use it in an ioctl and expect things to work
> properly.
I'm not disagreeing that it ought to use __u32, but are there any Linux
supported targets that don't have a 32-bit int? It's long that tends
to change size.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-05-12 0:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200405112211.i4BMBQDZ006167@hera.kernel.org>
2004-05-11 22:22 ` From Eric Anholt: Greg KH
2004-05-11 23:17 ` Dave Airlie
2004-05-11 23:20 ` Dave Airlie
2004-05-11 23:34 ` Valdis.Kletnieks
2004-05-11 23:43 ` Greg KH
2004-05-12 0:07 ` Daniel Jacobowitz [this message]
2004-05-12 0:12 ` Greg KH
2004-05-12 0:12 ` H. Peter Anvin
2004-05-11 23:46 ` ioctls in drm.h Dave Airlie
2004-05-13 1:39 ` From Eric Anholt: Eric Anholt
2004-05-12 1:07 ` Jon Smirl
2004-05-12 1:15 ` Greg KH
2004-05-12 22:32 ` Linus Torvalds
2004-05-13 16:54 ` Egbert Eich
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=20040512000709.GA10233@nevyn.them.org \
--to=dan@debian.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox