From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753869AbaIAMeH (ORCPT <rfc822;w@1wt.eu>);
	Mon, 1 Sep 2014 08:34:07 -0400
Received: from youngberry.canonical.com ([91.189.89.112]:45434 "EHLO
	youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753830AbaIAMeG (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 1 Sep 2014 08:34:06 -0400
Message-ID: <540467B7.4000801@canonical.com>
Date: Mon, 01 Sep 2014 14:33:59 +0200
From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: Dan Carpenter <dan.carpenter@oracle.com>
CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        devel@driverdev.osuosl.org, Daniel Vetter <daniel.vetter@ffwll.ch>,
        LKML <linux-kernel@vger.kernel.org>, Colin Cross <ccross@google.com>,
        "linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
        John Stultz <john.stultz@linaro.org>,
        Jesse Barnes <jbarnes@virtuousgeek.org>,
        Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [PATCH 2/2] android: add sync_fence_create_dma
References: <53EC8722.4070407@canonical.com> <53EC876C.9050705@canonical.com> <20140815064656.GB20920@kroah.com> <53FED20D.3030506@canonical.com> <20140828115747.GL5046@mwanda>
In-Reply-To: <20140828115747.GL5046@mwanda>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.

~Maarten