From: "Thomas Hellström" <thomas@shipmail.org>
To: Sam Ravnborg <sam@ravnborg.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: Sun, 14 Dec 2008 16:57:34 +0100 [thread overview]
Message-ID: <49452CEE.1090909@shipmail.org> (raw)
In-Reply-To: <20081213193506.GA22969@uranus.ravnborg.org>
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?
/Thomas
Sam Ravnborg wrote:
> Hi David et al.
>
> After improving the headers_check.pl script to do a
> check for files included with:
>
> #include "foo.h"
>
> it reported the following error:
>
> /home/sam/kernel/knext.git/usr/include/drm/via_drm.h:34: included file '/home/sam/kernel/knext.git/usr/include/drm/via_drmclient.h' is not exported
>
> And indeed the file via_drmclient.h does not exist in the kernel source.
> We do not see any issue in the kernel as the include is guarded by:
>
> #ifndef __KERNEL__
> #include "via_drmclient.h"
> #endif
>
> But referring to a non-existing file is not the right thing to to.
>
> We need this check as we have several places where we do:
>
> #include "foo.h"
>
> in our exported headers.
>
> So we need to fix drm somehow.
>
> The headers_check.pl patch is included for reference.
>
>
next prev parent reply other threads:[~2008-12-14 16:14 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 [this message]
2008-12-15 21:02 ` Sam Ravnborg
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=49452CEE.1090909@shipmail.org \
--to=thomas@shipmail.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.