From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v6 1/2] include: bump drm uAPI headers
Date: Thu, 8 Mar 2018 14:53:52 +0000 [thread overview]
Message-ID: <a808df48-7346-8dba-e887-e3a1edb4a9ac@intel.com> (raw)
In-Reply-To: <152052040577.18139.14400746339130608684@mail.alporthouse.com>
On 08/03/18 14:46, Chris Wilson wrote:
> Quoting Lionel Landwerlin (2018-03-08 14:39:59)
>> For testing only, to be updated with proper commit id from drm-next.
> Surely, we can declare this to be ready with
>
> commit c822e059185585f79b2007b1d2cafacf4264e610
> Author: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Date: Tue Mar 6 12:28:57 2018 +0000
>
> drm/i915: expose rcs topology through query uAPI
>
> ? Then this can land.
> -Chris
>
I was told by the drm gods that nothing should land in userspace before
it hits drm-next :/
At least that seems to be the rule for mesa.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-03-08 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 14:39 [igt-dev] [PATCH i-g-t v6 1/2] include: bump drm uAPI headers Lionel Landwerlin
2018-03-08 14:40 ` [igt-dev] [PATCH i-g-t v6 2/2] tests: add i915 query tests Lionel Landwerlin
2018-03-08 14:46 ` [igt-dev] [PATCH i-g-t v6 1/2] include: bump drm uAPI headers Chris Wilson
2018-03-08 14:53 ` Lionel Landwerlin [this message]
2018-03-08 15:03 ` Chris Wilson
2018-03-08 15:22 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v6,1/2] " Patchwork
2018-03-08 20:11 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=a808df48-7346-8dba-e887-e3a1edb4a9ac@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.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