public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Thomas Hellström" <thomas@shipmail.org>
Cc: David Airlie <airlied@linux.ie>,
	dri-devel <dri-devel@lists.sourceforge.net>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: BUG: via_drmclient.h is referenced but does not exist
Date: Mon, 15 Dec 2008 22:02:27 +0100	[thread overview]
Message-ID: <20081215210227.GA14396@uranus.ravnborg.org> (raw)
In-Reply-To: <49452CEE.1090909@shipmail.org>

On Sun, Dec 14, 2008 at 04:57:34PM +0100, Thomas Hellström wrote:
> Hi!
> 
> The intention is for via_drm.h to be self-containing when included both 
> for a kernel build and for a user-space build. In this particular case, 
> via_drmclient.h lives in the user-space clients and includes stdint.h to 
> get access to uint32_t and friends.
> 
> Of course, the user-space clients could
> #include "uint32.h"
> #include "via_drm.h"
> 
> but shouldn't really the tools be mimicing what the compiler does in 
> this case?

The kernel headers and thus the kernel ABI is separate and ideally
they should not depend on any other header files to provide anything.

This is why __u32, __u64 etc are preferred in the kernel ABI
and not uint32_t as used by the drm headers.

We do not adhere to this as a strict rule (yet).
But if you do:

grep -l uint32_t usr/include/linux

then you will only see 7 hits. Out of 368 files.
So we are not bad in this respect.

For drm the fix seems simple - just replace all of uint32_t with __u32.
likewise for the other 32 bit and the 64 bit variants.

For the specific case where drm includes a non-existing file I suggest
that we get this fixed in some way soon.

	Sam

  reply	other threads:[~2008-12-15 21:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13 19:35 BUG: via_drmclient.h is referenced but does not exist Sam Ravnborg
2008-12-14 15:57 ` Thomas Hellström
2008-12-15 21:02   ` Sam Ravnborg [this message]
2008-12-15 21:26     ` Thomas Hellström
2008-12-15 21:51       ` Sam Ravnborg

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=20081215210227.GA14396@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@shipmail.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