From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753511AbaIAMpu (ORCPT ); Mon, 1 Sep 2014 08:45:50 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:37373 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753017AbaIAMpt (ORCPT ); Mon, 1 Sep 2014 08:45:49 -0400 Date: Mon, 1 Sep 2014 15:45:19 +0300 From: Dan Carpenter To: Maarten Lankhorst Cc: devel@driverdev.osuosl.org, Greg Kroah-Hartman , LKML , Colin Cross , "linaro-mm-sig@lists.linaro.org" , John Stultz , Jesse Barnes , Daniel Vetter , Sumit Semwal Subject: Re: [PATCH 2/2] android: add sync_fence_create_dma Message-ID: <20140901124519.GH5122@mwanda> References: <53EC8722.4070407@canonical.com> <53EC876C.9050705@canonical.com> <20140815064656.GB20920@kroah.com> <53FED20D.3030506@canonical.com> <20140828115747.GL5046@mwanda> <540467B7.4000801@canonical.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <540467B7.4000801@canonical.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 01, 2014 at 02:33:59PM +0200, Maarten Lankhorst wrote: > Hey, > > Op 28-08-14 om 13:57 schreef Dan Carpenter: > > On Thu, Aug 28, 2014 at 08:54:05AM +0200, Maarten Lankhorst wrote: > >> Hey, > >> > >> On 15-08-14 08:46, Greg Kroah-Hartman wrote: > >>> On Thu, Aug 14, 2014 at 11:54:52AM +0200, Maarten Lankhorst wrote: > >>>> This allows users of dma fences to create a android fence. > >>> Who is going to use these functions? I need an in-kernel user before I > >>> can add new api calls. > >> So I found a in-kernel user and PATCH 1/2 fixes a mem-leak with android out of tree drivers, and android's in-kernel sw-sync. > >> Will you apply these patches? > > Can you resend the patches? Fix the changelog of the first one to > > mention that it is a bugfix. Send a [patch 3/3] which uses the new > > functions in [patch 2/3]. > The second patch will have to be applied without an in-kernel user because it > will be used in the drm subsystem, by someone other than me. Their code is not > ready yet, but will likely will be for the 3.18 merge window. Let's just wait until the user is ready. It might be easiest if they push your patch? Anyway, please resend the first patch so we can apply that right away. regards, dan carpenter