From: Andres Rodriguez <andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Deucher,
Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>,
Emil Velikov
<emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: amd-gfx mailing list
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH 1/3] headers: Sync {amdgpu,radeon}_drm.h with the kernel
Date: Mon, 9 Jan 2017 13:07:05 -0500 [thread overview]
Message-ID: <3a22004d-536c-dec9-72f5-3a9c195d72ba@gmail.com> (raw)
In-Reply-To: <BN6PR12MB165210337024334D288C5F42F7640-/b2+HYfkarQqUD6E6FAiowdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
On 2017-01-09 01:00 PM, Deucher, Alexander wrote:
>> -----Original Message-----
>> From: amd-gfx [mailto:amd-gfx-bounces@lists.freedesktop.org] On Behalf
>> Of Andres Rodriguez
>> Sent: Monday, January 09, 2017 12:01 PM
>> To: Emil Velikov
>> Cc: amd-gfx mailing list
>> Subject: Re: [PATCH 1/3] headers: Sync {amdgpu,radeon}_drm.h with the
>> kernel
>>
>>
>>
>> On 2017-01-09 11:23 AM, Emil Velikov wrote:
>>> Thank you Andres. There's a small nit below.
>>>
>>> On 5 January 2017 at 00:29, Andres Rodriguez <andresx7@gmail.com>
>> wrote:
>>>> Generated using make headers_install from:
>>>> airlied/drm-next 2cf026a Merge branch 'linux-4.10' ...
>>>>
>>>> Manually re-added missing RADEON_TILING_R600_NO_SCANOUT as
>> documented on
>>>> README
>>>>
>>> "Thou Shalt Not make any manual changes to include/drm/*h"
>>>
>>> Please check if there's released open-source userspace which depends
>>> on this. If there's none just drop it all together, alternatively
>>> please update the kernel header(s).
>> Gallium in mesa depends on this, so I'll update the kernel headers
>> accordingly.
> IIRC, these are not required for the ioctls, they were just put in here since the header is shared between multiple userspace components.
>
> Alex
Would it still be okay to add it to the kernel side then? Having
multiple userspace components depend on it would make it complicated to
get a patch merged into each of them.
Andres
>> Thanks again for pointing me to the README, it was pretty useful.
>>
>> Regards,
>> Andres
>>
>>> Thanks
>>> Emil
>> _______________________________________________
>> amd-gfx mailing list
>> amd-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-01-09 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 0:29 [PATCH v3] libdrm changes for high priority contexts Andres Rodriguez
[not found] ` <20170105002935.5796-1-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-05 0:29 ` [PATCH 1/3] headers: Sync {amdgpu,radeon}_drm.h with the kernel Andres Rodriguez
[not found] ` <20170105002935.5796-2-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-09 16:23 ` Emil Velikov
[not found] ` <CACvgo50x_z1XrM-V2jvYf3e3zp4muy0Wyxpimk_5zM9hof28PQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-09 17:01 ` Andres Rodriguez
[not found] ` <d5029218-6760-ef97-3dd6-632ad51dc966-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-09 18:00 ` Deucher, Alexander
[not found] ` <BN6PR12MB165210337024334D288C5F42F7640-/b2+HYfkarQqUD6E6FAiowdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-01-09 18:07 ` Andres Rodriguez [this message]
2017-01-05 0:29 ` [PATCH 2/3] headers: add new context priority parameter to amdgpu_drm.h Andres Rodriguez
[not found] ` <20170105002935.5796-3-andresx7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-09 16:28 ` Emil Velikov
[not found] ` <CACvgo53xrtLkCVj4xcZ7BzrsFWXJMBLMqNFkgYau3Gro-3KDjg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-09 17:04 ` Andres Rodriguez
2017-01-05 0:29 ` [PATCH 3/3] amdgpu: implement context priority for amdgpu_cs_ctx_create2 v3 Andres Rodriguez
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=3a22004d-536c-dec9-72f5-3a9c195d72ba@gmail.com \
--to=andresx7-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox