From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Hellstrom Subject: Re: drm-next update Date: Tue, 20 Nov 2012 13:34:28 +0100 Message-ID: <50AB78D4.2020602@vmware.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com [208.91.2.12]) by gabe.freedesktop.org (Postfix) with ESMTP id A81B6E623E for ; Tue, 20 Nov 2012 04:34:31 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org, Dave Airlie List-Id: dri-devel@lists.freedesktop.org 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