dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thomas@shipmail.org>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
	linux-graphics-maintainer@vmware.com,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: vmwgfx GL3 and other -next (4.3) pathches
Date: Fri, 21 Aug 2015 14:42:39 +0200	[thread overview]
Message-ID: <55D71CBF.3020705@shipmail.org> (raw)
In-Reply-To: <CACvgo50AR8APCKGbh06Z8NxogDhd+aCdO0U9jeeL1jtwjenmzg@mail.gmail.com>

Hi, Emil

On 08/21/2015 02:31 PM, Emil Velikov wrote:
> Hi Thomas,
>
> On 14 August 2015 at 12:29, Thomas Hellstrom <thellstrom@vmware.com> wrote:
>> On 08/13/2015 08:38 AM, Daniel Vetter wrote:
>>> On Thu, Aug 13, 2015 at 7:04 AM, Thomas Hellstrom <thellstrom@vmware.com> wrote:
>>>>> Out of curiosity I did take a (very) quick look and also tried to find the
>>>>> corresponding userspace parts. On a quick search I didn't find anything
>>>>> for libdrm or mesa, neither on mailing lists or already committed. Where
>>>>> are those pieces?
>>>>> -Daniel
>>>> The mesa code is ready and working but undergoing final tidying before
>>>> upstreaming. The aim is of course to release it well before linux 4.3 is
>>>> out. However our kernel interface has just undergone very minor change
>>> In my opinion userspace must be ready for merging (and public) before
>>> the kernel code can go in. That's at least what I enforce for i915 and
>>> how all other drivers are handled.
>>> -Daniel
>> OK, so the mesa code has now been published here:
>>
>> http://cgit.freedesktop.org/~thomash/mesa/log/?h=svga-gl3-merge
>>
>> While it's in principle ready for merging, it lacks some final reviewing
>> and testing but otherwise should work fine.
>>
> I cannot see the series ever making it to the (mesa-dev) mailing list.
> Did it got stuck due to its size or you forgot to send it over ?
> Mildly related - the mesa 11.0 branchpoint is just a few hours away,
> so it seems that this work will miss it :(

The reason is basically because I want to get a final internal review
and go-ahead. Unfortunately I wasn't aware that the mesa 11.0
branchpoint was immediately upcoming. I guess there's not much we can do
about it at this point? Even if I post the patches now we can't just
expect them to be reviewed within a couple of hours...

Thomas

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


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

  reply	other threads:[~2015-08-21 12:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 18:31 vmwgfx GL3 and other -next (4.3) pathches Thomas Hellstrom
2015-08-12 21:02 ` Daniel Vetter
2015-08-13  5:06   ` Thomas Hellstrom
2015-08-12 21:07 ` Daniel Vetter
2015-08-13  5:04   ` Thomas Hellstrom
2015-08-13  6:38     ` Daniel Vetter
2015-08-13  7:18       ` Thomas Hellstrom
2015-08-14 11:29       ` Thomas Hellstrom
2015-08-21 12:31         ` Emil Velikov
2015-08-21 12:42           ` Thomas Hellstrom [this message]
2015-08-21 14:39             ` Emil Velikov
2015-08-21 14:43               ` Thomas Hellstrom
2015-08-21 14:51               ` Ilia Mirkin
2015-08-13 11:47 ` Emil Velikov
2015-08-13 12:07   ` Thomas Hellstrom

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=55D71CBF.3020705@shipmail.org \
    --to=thomas@shipmail.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=linux-graphics-maintainer@vmware.com \
    --cc=thellstrom@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox