[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFyOHtbPj9OBEOcdH=K6dnmYNaS91yvfdmCTBtuN5OdD3g@mail.gmail.com>
Date: Mon, 23 May 2016 12:10:25 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Dave Airlie <airlied@...ux.ie>
Cc: DRI mailing list <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [git pull] drm for v4.7
On Mon, May 23, 2016 at 11:59 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> I'll test this out and look what happens, but I hate getting different
> results than what I'm told to expect.
Hmm. I also get a lot of
./usr/include/drm/amdgpu_drm.h:38: userspace cannot reference
function or variable defined in the kernel
./usr/include/drm/drm.h:63: userspace cannot reference function or
variable defined in the kernel
./usr/include/drm/drm.h:699: userspace cannot reference function or
variable defined in the kernel
...
warnings with my allmodconfig build. They do seem to be due to
checkpatch not really grokking the
#if defined(__cplusplus)
extern "C" {
#endif
and thinking that's a sign of a kernel function or variable
declaration being exported to user space, but it's a bit annoying.
Is there a patch pending for this that I'm not aware of, or is it just
that nobody but me hates spurious warnings? Didn't this show up in
linux-next? And if it _did_ show up in linux-next, why was the pull
request not talking about it?
Linus
Powered by blists - more mailing lists