From: Tanmay Shah <tanmay@codeaurora.org>
To: Eric Anholt <eric@anholt.net>
Cc: ryadav@codeaurora.org, seanpaul@google.com,
manojavm@codeaurora.org, dri-devel@lists.freedesktop.org,
hoegsberg@google.com, chandanu@codeaurora.org
Subject: Re: [PATCH libdrm] msm: add msm drm uapi header
Date: Tue, 24 Jul 2018 14:11:05 -0700 [thread overview]
Message-ID: <4bc8aa6b9d8474bb6712cf8d7899f158@codeaurora.org> (raw)
In-Reply-To: <87pnzcfnm6.fsf@anholt.net>
On 2018-07-24 12:19, Eric Anholt wrote:
> Tanmay Shah <tanmay@codeaurora.org> writes:
>
>> file derived from msm-next kernel uapi header.
>
> Unless there's an exception from Dave, I believe uapi headers in libdrm
> and Mesa should be direct copies from "make headers_install" on the
> drm-next branch. How does this compare to that?
The header file is identical as in drm-next kernel.
--
Tanmay Shah
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-07-24 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 18:55 [PATCH libdrm] msm: add msm drm uapi header Tanmay Shah
2018-07-24 19:19 ` Eric Anholt
2018-07-24 21:11 ` Tanmay Shah [this message]
2018-07-24 22:21 ` Eric Anholt
2018-07-26 0:33 ` Tanmay Shah
[not found] ` <d778744ff473a941da1570241575fc38@codeaurora.org>
[not found] ` <CAF6AEGtz48hJbav6h0tJembxT-R0G4QMBuAwtU=Mb4RWTouhbA@mail.gmail.com>
2018-07-26 1:05 ` Tanmay Shah
2018-08-09 23:29 ` [PATCH libdrm v2] libdrm: " Tanmay Shah
[not found] ` <1533857366-13080-1-git-send-email-tanmay-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-08-10 22:02 ` Eric Anholt
2018-08-14 0:29 ` [PATCH libdrm v3] " Tanmay Shah
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=4bc8aa6b9d8474bb6712cf8d7899f158@codeaurora.org \
--to=tanmay@codeaurora.org \
--cc=chandanu@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=hoegsberg@google.com \
--cc=manojavm@codeaurora.org \
--cc=ryadav@codeaurora.org \
--cc=seanpaul@google.com \
/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.