From: Daniel Vetter <daniel@ffwll.ch>
To: Emil Velikov <emil.l.velikov@gmail.com>
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 10:38:24 +0100 [thread overview]
Message-ID: <20160127093824.GI11240@phenom.ffwll.local> (raw)
In-Reply-To: <CACvgo51bnRxfG0QzoFZ=16cYsM+iXj_OWL2U-EuHK_x_uThn0Q@mail.gmail.com>
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.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-01-27 9:38 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 [this message]
2016-01-27 11:42 ` Daniel Stone
2016-01-27 13:28 ` Emil Velikov
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=20160127093824.GI11240@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--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.