From: Eric Anholt <eta@lclark.edu>
To: DRI <dri-devel@lists.sourceforge.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: From Eric Anholt:
Date: Wed, 12 May 2004 18:39:10 -0700 [thread overview]
Message-ID: <1084412350.774.75.camel@leguin> (raw)
In-Reply-To: <200405112334.i4BNYdjO018918@turing-police.cc.vt.edu>
On Tue, 2004-05-11 at 16:34, 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)?
These headers being discussed are what define the interface between
userland and kernel, and nothing else. They are included by both
userland (libdrm, statically linked in the 3d drivers and in the X
server) and kernel.
--
Eric Anholt eta@lclark.edu
http://people.freebsd.org/~anholt/ anholt@FreeBSD.org
next prev parent reply other threads:[~2004-05-13 1:31 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
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 ` Eric Anholt [this message]
2004-05-12 1:07 ` From Eric Anholt: 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=1084412350.774.75.camel@leguin \
--to=eta@lclark.edu \
--cc=dri-devel@lists.sourceforge.net \
--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