All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov@gmail.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: ML dri-devel <dri-devel@lists.freedesktop.org>,
	Emmanuel Gil Peyrot <emmanuel.peyrot@collabora.com>
Subject: Re: [PATCH libdrm] Synchronize drm/drm_fourcc.h with Linux’ version
Date: Wed, 27 Jan 2016 13:28:04 +0000	[thread overview]
Message-ID: <CACvgo521C5r0vPar8BJBrxLo46CHuomjjpz2DuvewxzTTNENiQ@mail.gmail.com> (raw)
In-Reply-To: <CAPj87rPJz2tezgz2gEDB=wNHX3Q9FenyTkQTNCLreh85ekfTiA@mail.gmail.com>

On 27 January 2016 at 11:42, Daniel Stone <daniel@fooishbar.org> wrote:
> Hey,
>
> On 27 January 2016 at 09:38, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Tue, Jan 26, 2016 at 09:04:18PM +0000, Emil Velikov wrote:
>>> On 11 January 2016 at 19:32, Emmanuel Gil Peyrot
>>> <emmanuel.peyrot@collabora.com> wrote:
>>> > This adds R8, RG88 and GR88, as well as the non-subsampled NV24/NV42 formats.
>>> >
>>> Err... please don't copy/paste 'random' hunks here. These headers
>>> should be imported from the kernel with the commit message mentioning
>>> the sha of their origin.
>>>
>>> I've been procrastinating^Wwaiting on some upstream changes to land
>>> and with those in place I'll update the Makefile to import things
>>> properly.
>>
>> Yeah, we should have some scripts in libdrm that runs make
>> headers_install, copies over the latest generated uapi headers for drm and
>> then creates a commit with the sha1 it was generated from. Maybe even a
>> rule that the sha1 has to be from Dave's drm-next.
>
> Yeah, it's certainly doable, once some kernel-internal details are
> shuffled out of uapi/drm/drm_mode.h.
What do you have in mind - DRM_MODE_PICTURE_ASPECT_* ? I'm thinking
more that we should bring back DRM_MODE_OBJECT_* as it breaks libdrm
and maybe other userspace.

Feel free to let me know here or in the patch I just sent (didn't
realise and I Cc'd your collabora email).

Thanks
Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-01-27 13:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 19:32 [PATCH libdrm] Synchronize drm/drm_fourcc.h with Linux’ version Emmanuel Gil Peyrot
2016-01-26 21:04 ` Emil Velikov
2016-01-27  9:38   ` Daniel Vetter
2016-01-27 11:42     ` Daniel Stone
2016-01-27 13:28       ` Emil Velikov [this message]
2016-01-27 13:31         ` Daniel Stone
2016-01-27 14:23           ` Emil Velikov
2016-01-27 14:26             ` Daniel Stone
  -- strict thread matches above, loose matches on Subject: below --
2016-01-11 19:17 Emmanuel Gil Peyrot

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=CACvgo521C5r0vPar8BJBrxLo46CHuomjjpz2DuvewxzTTNENiQ@mail.gmail.com \
    --to=emil.l.velikov@gmail.com \
    --cc=daniel@fooishbar.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emmanuel.peyrot@collabora.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.