linux-kernel - Re: [PATCH v2 0/9] Updated fence patch series

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAO_48GHwJ4EuCKgLmZhEaEQqS9e7EVZP3hsivhRwLCNFhzAQVA@mail.gmail.com>
Date:	Tue, 8 Jul 2014 20:22:11 +0530
From:	Sumit Semwal <sumit.semwal@...aro.org>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Maarten Lankhorst <maarten.lankhorst@...onical.com>,
	"open list:GENERIC INCLUDE/A..." <linux-arch@...r.kernel.org>,
	Thomas Hellstrom <thellstrom@...are.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	dri-devel <dri-devel@...ts.freedesktop.org>,
	"linaro-mm-sig@...ts.linaro.org" <linaro-mm-sig@...ts.linaro.org>,
	"Clark, Rob" <robdclark@...il.com>,
	Thierry Reding <thierry.reding@...il.com>,
	Colin Cross <ccross@...gle.com>,
	"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>
Subject: Re: [PATCH v2 0/9] Updated fence patch series

On 8 July 2014 20:09, Greg KH <gregkh@...uxfoundation.org> 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 <gregkh@...uxfoundation.org> 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'!

Upto you!
> thanks,
>
> greg k-h
Thanks and best regards,
~Sumit


-- 
Thanks and regards,

Sumit Semwal
Graphics Engineer - Graphics working group
Linaro.org │ Open source software for ARM SoCs
--
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/