Re: drm-next update

[Thomas Hellstrom <thellstrom@vmware.com>]

On 11/20/2012 07:39 AM, Dave Airlie wrote:
> Okay just pushed out a bunch of -next queued stuff,
>
> I've been stuck on another project for a couple of weeks and haven't
> really being paying enough attention to -next, so this is a heads up,
> if someone has something big they want merged this window and I
> haven't seen it yet or merged it yet, you should probably mention it
> in a reply to this mail with a summary of where you think its at.
> (e.g. atomic nuclear modesetting flipping).
>
> personal messages follow:
>
> Thomas:
> I merged some of the vmware patches I saw, I got to
> [6/8] drm/vmwgfx: Refactor resource management
> it didn't apply, it wasn't trivial, so you need to resend the 6/7/8 on
> top of this tree, or point me to what I missed that makes it all
> magically work!
>
It appears they conflicted with the TTM sync_obj_arg removal patches.
Please apply

[PATCH -next 0/5] drm/ttm: Get rid of a number of atomic 
read-modify-write ops addons
(This is the diff for the latest version of Get rid of a number of 
atomic read-modify-write ops)

[PATCH -next 0/3] vmwgfx stuff for -next rebased
(This is the patches 6/8 that didn't apply previously)

[PATCH -next] drm/ttm: Optimize vm locking using kref_get_unless_zero
(Small patch that gets rid of a write lock around buffer object 
unreferences)

Thanks,
Thomas