dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Tanmay Shah <tanmay@codeaurora.org>
To: Rob Clark <robdclark@gmail.com>
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: Wed, 25 Jul 2018 18:05:06 -0700	[thread overview]
Message-ID: <4edbde4f5467c9f8e36b37df8bc8a3d9@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGtz48hJbav6h0tJembxT-R0G4QMBuAwtU=Mb4RWTouhbA@mail.gmail.com>

On 2018-07-25 17:56, Rob Clark wrote:
> On Wed, Jul 25, 2018 at 8:43 PM, Tanmay Shah <tanmay@codeaurora.org> 
> wrote:
>> On 2018-07-25 17:33, Tanmay Shah wrote:
>>> 
>>> On 2018-07-24 15:21, Eric Anholt wrote:
>>>> 
>>>> Tanmay Shah <tanmay@codeaurora.org> writes:
>>>> 
>>>>> 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.
>>>> 
>>>> 
>>>> Great, let's say "drm-next" instead to make that clear.  Also, looks
>>>> like freedreno/msm/msm_drm.h should probably get removed in favor of
>>>> this?
>>>> 
>>>> _______________________________________________
>>>> dri-devel mailing list
>>>> dri-devel@lists.freedesktop.org
>>>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>>> 
>>> 
>>> +Rob Clark
>>> 
>>> Thanks Eric, I will send v2 with suggested changes.
>>> 
>>> freedreno/msm/msm_drm.h is owned by Rob, I am not sure if we need it 
>>> there
>>> or not. I would let Rob comment on this.
>>> 
>>> We require msm_drm.h in include/drm/ directory to export GEM ioctls 
>>> so
>>> other modules
>>> such as gbm can use it. Other platforms have similar strategy.
>> 
>> 
>> Sorry, Actually +Rob Clark
> 
> yeah, we should remove the duplicate header in libdrm.. so far it
> hasn't been exported outside of libdrm_freedreno since it was
> unneeded.. but as long as libdrm_freedreno still compiles properly
> with the moved header, I'm fine with it.  There might be some include
> path tweaking required, not sure..
> 
> (and PS. "ownership" is not a thing upstream.. if it lives in the same
> git tree and changing it doesn't break the build, it is not off-limits
> ;-))
> 
> BR,
> -R

Thanks, Rob.
-- 
Tanmay Shah
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-07-26  1:05 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
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 [this message]
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=4edbde4f5467c9f8e36b37df8bc8a3d9@codeaurora.org \
    --to=tanmay@codeaurora.org \
    --cc=chandanu@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hoegsberg@google.com \
    --cc=manojavm@codeaurora.org \
    --cc=robdclark@gmail.com \
    --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 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).