On Tue, Jul 01, 2014 at 12:57:02PM +0200, Maarten Lankhorst wrote: > So after some more hacking I've moved dma-buf to its own subdirectory, > drivers/dma-buf and applied the fence patches to its new place. I believe that the > first patch should be applied regardless, and the rest should be ready now. > :-) > > Changes to the fence api: > - release_fence -> fence_release etc. > - __fence_init -> fence_init > - __fence_signal -> fence_signal_locked > - __fence_is_signaled -> fence_is_signaled_locked > - Changing BUG_ON to WARN_ON in fence_later, and return NULL if it triggers. > > 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? thanks, greg k-h _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
