All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: 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: Thu, 13 Aug 2015 07:06:49 +0200	[thread overview]
Message-ID: <55CC25E9.6030307@vmware.com> (raw)
In-Reply-To: <20150812210210.GQ17734@phenom.ffwll.local>

On 08/12/2015 11:02 PM, Daniel Vetter wrote:
> On Wed, Aug 12, 2015 at 08:31:09PM +0200, Thomas Hellstrom wrote:
>> Hi, all,
>>
>> I've pushed the current upcoming vmwgfx patches for 4.3 into
>>
>> git://people.freedesktop.org/~thomash/linux
>> branch vmwgfx-next for review.
>>
>> There are quite a few patches so I figured that this would be easier
>> than posting all patches on the mailing list.
>> The patches are all internally reviewed, either by me, Sinclair Yeh,
>> Brian Paul or Charmaine Lee.
>>
>> The patchset basically enables the following
>> - Screen targets - Use of a new device API for scanout buffers
>> - Command buffers - A device command buffer queue replacing the old ring
>> fifo.
>> - GL3 - support for a new device functionality called "DX" that enables
>> us to support GL3. Mesa gallium driver support for GL3 is about to be
>> published. The patches for DX support have been heavily squashed.
>>
>> Please let me know if anybody has any objections against this.
> Just submit it to dri-devel, it's really not that much compared to other
> big patch series here ;-)
> -Daniel
OK, I'll do that. I spoke briefly to Dave some time ago and he suggested
using a tree in this way, unless someone on dri-devel objected.

Thanks,
Thomas.

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

  reply	other threads:[~2015-08-13  5:06 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 [this message]
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
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=55CC25E9.6030307@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-graphics-maintainer@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 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.