lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 1 Sep 2014 15:45:19 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Maarten Lankhorst <maarten.lankhorst@...onical.com>
Cc:	devel@...verdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Colin Cross <ccross@...gle.com>,
	"linaro-mm-sig@...ts.linaro.org" <linaro-mm-sig@...ts.linaro.org>,
	John Stultz <john.stultz@...aro.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Sumit Semwal <sumit.semwal@...aro.org>
Subject: Re: [PATCH 2/2] android: add sync_fence_create_dma

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists