Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754810AbaGHRrz (ORCPT ); Tue, 8 Jul 2014 13:47:55 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:34955 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753427AbaGHRrx (ORCPT ); Tue, 8 Jul 2014 13:47:53 -0400 Date: Tue, 8 Jul 2014 10:52:17 -0700 From: Greg KH To: Sumit Semwal Cc: Maarten Lankhorst , "open list:GENERIC INCLUDE/A..." , Thomas Hellstrom , Linux Kernel Mailing List , dri-devel , "linaro-mm-sig@lists.linaro.org" , "Clark, Rob" , Thierry Reding , Colin Cross , "linux-media@vger.kernel.org" Subject: Re: [PATCH v2 0/9] Updated fence patch series Message-ID: <20140708175217.GA11121@kroah.com> References: <20140701103432.12718.82795.stgit@patser> <20140702053758.GA7578@kroah.com> <20140707173052.GA8693@kroah.com> <20140708134427.GG17271@phenom.ffwll.local> <20140708143912.GA3436@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 08, 2014 at 08:22:11PM +0530, Sumit Semwal wrote: > On 8 July 2014 20:09, Greg KH wrote: > > On Tue, Jul 08, 2014 at 03:44:27PM +0200, Daniel Vetter wrote: > >> On Mon, Jul 07, 2014 at 10:30:52AM -0700, Greg KH wrote: > >> > On Mon, Jul 07, 2014 at 03:23:17PM +0200, Daniel Vetter wrote: > >> > > On Wed, Jul 2, 2014 at 7:37 AM, Greg KH wrote: > >> > > >> Android can expose fences to userspace. It's possible to make the new fence > >> > > >> mechanism expose the same fences to userspace by changing sync_fence_create > >> > > >> to take a struct fence instead of a struct sync_pt. No other change is needed, > >> > > >> because only the fence parts of struct sync_pt are used. But because the > >> > > >> userspace fences are a separate problem and I haven't really looked at it yet > >> > > >> I feel it should stay in staging, for now. > >> > > > > >> > > > Ok, that's reasonable. > >> > > > > >> > > > At first glance, this all looks "sane" to me, any objection from anyone > >> > > > if I merge this through my driver-core tree for 3.17? > >> > > > >> > > Ack from my side fwiw. > >> > > >> > Thanks, I'll queue it up later today. > >> > >> btw should we add you as a (co)maintainer for driver/core/dma-buf since > >> you seem to want to keep a closer tab on what the insane gfx folks are up > >> to in there? > > > > Sure, why not, what's one more maintainership... > > > > Oh, does that mean you want me to be the one collecting the patches and > > forwarding them on to Linus? If so, that's fine, I can easily do that > > as well due to my infrastructure being set up for it. > > > If you're ok, I could continue to do the collecting / forwarding > business - I guess Daniel meant more from the 'not miss patches that > need review'! Hey, I'm more than willing to have other people do the real work of collecting / forwarding :) I'll just review stuff as it floats by, that's not enough of a role to put me in "MAINTAINERS" at all. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/