All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Petri Latvala <petri.latvala@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 0/5] Import drm UAPI headers.
Date: Mon, 20 Nov 2017 11:41:06 +0100	[thread overview]
Message-ID: <20171120104106.tm66zib527jkzabg@phenom.ffwll.local> (raw)
In-Reply-To: <20171113114022.ghtwwolfjivhehjf@platvala-desk.ger.corp.intel.com>

On Mon, Nov 13, 2017 at 01:40:22PM +0200, Petri Latvala wrote:
> On Sat, Nov 11, 2017 at 12:27:15AM +0000, Lionel Landwerlin wrote:
> > Hey Eric,
> > 
> > Like it did for Mesa I think this makes developers' lives easier.
> > Not having to update libdrm and then compile against the right version just
> > for the kernel headers you need is a win (in my opinion).
> 
> Yes indeed. Would be nice to be able to build IGT on Debian stable
> again.
> 
> Series is
> 
> Acked-by: Petri Latvala <petri.latvala@intel.com>
> 
> Some more acks (or objections, if any) for the overall idea would be
> nice to have, after that we can merge this and start cleaning up the
> LOCAL_* crud.

fwiw I like the idea of just importing the headers, avoids all the need
for _local versions. Of course we need to make sure we don't add stuff
that isn't upstream, usually uapi merging rules apply (i.e. merge kernel,
then merge userspace, how to CI tbh).

Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-20 10:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 21:26 [PATCH i-g-t 0/5] Import drm UAPI headers Eric Anholt
2017-11-10 21:26 ` [PATCH i-g-t 1/5] headers: Import drm-next uapi headers Eric Anholt
2017-11-10 21:26 ` [PATCH i-g-t 2/5] tests: Convert to using the imported drm-uapi headers Eric Anholt
2017-11-11  0:18   ` Lionel Landwerlin
2017-11-13 20:59     ` Eric Anholt
2017-11-10 21:26 ` [PATCH i-g-t 3/5] tests: Remove libdrm_vc4 dependency Eric Anholt
2017-11-22 10:37   ` Petri Latvala
2017-11-10 21:26 ` [PATCH i-g-t 4/5] lib: Use the imported uapi's addfb2 defines Eric Anholt
2017-11-10 21:26 ` [PATCH i-g-t 5/5] lib: Use drm-uapi/i915_drm.h instead of local defines Eric Anholt
2017-11-10 21:44 ` ✓ Fi.CI.BAT: success for Import drm UAPI headers Patchwork
2017-11-10 23:04 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-11-11  0:27 ` [PATCH i-g-t 0/5] " Lionel Landwerlin
2017-11-13 11:40   ` Petri Latvala
2017-11-20 10:41     ` Daniel Vetter [this message]
2017-11-20 20:06     ` Eric Anholt
2017-11-21  9:05       ` Daniel Vetter

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=20171120104106.tm66zib527jkzabg@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=petri.latvala@intel.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.