From: Eric Anholt <eric@anholt.net>
To: "Michel Dänzer" <michel@daenzer.net>,
"Emil Velikov" <emil.l.velikov@gmail.com>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 3/9] drm/vc4: Add create and map BO ioctls.
Date: Mon, 07 Dec 2015 20:05:57 -0800 [thread overview]
Message-ID: <87zixleg9m.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <566646EB.3050406@daenzer.net>
[-- Attachment #1.1: Type: text/plain, Size: 696 bytes --]
Michel Dänzer <michel@daenzer.net> writes:
> On 08.12.2015 10:16, Eric Anholt wrote:
>> Emil Velikov <emil.l.velikov@gmail.com> writes:
>>
>>> Hi Eric,
>>>
>>> A couple of suggestions/requests on the UAPI header side
>>>
>>> On 1 December 2015 at 20:35, Eric Anholt <eric@anholt.net> wrote:
>>>
>>>> --- /dev/null
>>>> +++ b/include/uapi/drm/vc4_drm.h
>>>
>>>> +#include <drm/drm.h>
>>>> +
>>> Can we make this a "drm.h" ?
>>
>> Nope.
>>
>> include/uapi/drm/vc4_drm.h:27:17: fatal error: drm.h: No such file or directory
>
> What happened to include/uapi/drm/drm.h in that tree?
Looks like it's just <drm.h> versus "drm.h" failure. I've changed over
to "drm.h"
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-12-08 4:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 20:35 [PATCH 1/9] drm: Create a driver hook for allocating GEM object structs Eric Anholt
2015-12-01 20:35 ` [PATCH 2/9] drm/vc4: Add a BO cache Eric Anholt
2015-12-01 20:35 ` [PATCH 3/9] drm/vc4: Add create and map BO ioctls Eric Anholt
2015-12-04 14:29 ` Emil Velikov
2015-12-08 1:16 ` Eric Anholt
2015-12-08 2:56 ` Michel Dänzer
2015-12-08 4:05 ` Eric Anholt [this message]
2015-12-01 20:35 ` [PATCH 4/9] drm/vc4: Add an API for creating GPU shaders in GEM BOs Eric Anholt
2015-12-02 11:35 ` Emil Velikov
2015-12-02 19:24 ` Eric Anholt
2015-12-01 20:35 ` [PATCH 5/9] drm/vc4: Fix a typo in a V3D debug register Eric Anholt
2015-12-01 20:35 ` [PATCH 6/9] drm/vc4: Bind and initialize the V3D engine Eric Anholt
2015-12-01 20:35 ` [PATCH 7/9] drm/vc4: Add support for drawing 3D frames Eric Anholt
2015-12-02 11:29 ` Emil Velikov
2015-12-02 19:27 ` Eric Anholt
2015-12-01 20:35 ` [PATCH 8/9] drm/vc4: Add support for async pageflips Eric Anholt
2015-12-02 14:05 ` Daniel Stone
2015-12-04 1:42 ` Eric Anholt
2015-12-07 10:13 ` Daniel Stone
2015-12-01 20:35 ` [PATCH 9/9] drm/vc4: Add an interface for capturing the GPU state after a hang Eric Anholt
2015-12-02 11:45 ` Emil Velikov
2015-12-02 19:35 ` Eric Anholt
2015-12-02 22:26 ` Daniel Vetter
2015-12-02 22:58 ` Daniel Stone
2015-12-03 11:55 ` Emil Velikov
2015-12-03 11:46 ` Emil Velikov
2015-12-02 8:58 ` [PATCH 1/9] drm: Create a driver hook for allocating GEM object structs Daniel Vetter
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=87zixleg9m.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
/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;
as well as URLs for NNTP newsgroup(s).