From: Eric Anholt <eta@lclark.edu>
To: arjanv@redhat.com
Cc: Dave Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org,
DRI <dri-devel@lists.sourceforge.net>
Subject: Re: drm - first steps towards 64-bit correctness..
Date: Sat, 31 Jul 2004 02:57:17 -0700 [thread overview]
Message-ID: <1091267836.425.46.camel@leguin> (raw)
In-Reply-To: <1091267687.2819.3.camel@laptop.fenrus.com>
On Sat, 2004-07-31 at 02:54, Arjan van de Ven wrote:
> On Sat, 2004-07-31 at 11:32, Eric Anholt wrote:
> > As long as you don't use the linux-y
> > "u32"-type types, BSD should be happy with the changes.
>
> can you explain why u32 would be outlawed? Surely it's trivial to do a
> typedef for u32 on BSD for drm ??
If there are nice standard types (uint32_t or u_int32_t, can't remember
which at the moment, I mentioned it in an email some time ago) out there
already that linux has too, why not use those?
--
Eric Anholt eta@lclark.edu
http://people.freebsd.org/~anholt/ anholt@FreeBSD.org
next prev parent reply other threads:[~2004-07-31 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-31 9:13 drm - first steps towards 64-bit correctness Dave Airlie
2004-07-31 9:32 ` Eric Anholt
2004-07-31 9:54 ` Arjan van de Ven
2004-07-31 9:57 ` Eric Anholt [this message]
2004-07-31 10:06 ` William Lee Irwin III
2004-07-31 11:02 ` Dave Airlie
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=1091267836.425.46.camel@leguin \
--to=eta@lclark.edu \
--cc=airlied@linux.ie \
--cc=arjanv@redhat.com \
--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 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.