GNOME Bugzilla – Bug 754833
dmabuf & fdmemory: fix allocator_alloc documentation
Last modified: 2015-09-23 14:03:05 UTC
gst_dmabuf_allocator_alloc() and gst_fd_allocator_alloc() documentation say we can pass a NULL allocator, which is not the case.
Created attachment 311071 [details] [review] dmabuf: remove 'allow-none' annotation in gst_dmabuf_allocator_alloc() doc
Created attachment 311072 [details] [review] fdmemory: remove 'allow-none' annotation in gst_fd_allocator_alloc() doc
Make sense, that's clearly a copy paste from the gst_allocator_alloc().
As it only changes documentation, we may merge it for 1.6 release if there is no objection.
Yes, that change is correct, and will actually prevent a crash from interpreted language like python and JS. Attachment 311071 [details] pushed as 4559feb - dmabuf: remove 'allow-none' annotation in gst_dmabuf_allocator_alloc() doc Attachment 311072 [details] pushed as 94e0279 - fdmemory: remove 'allow-none' annotation in gst_fd_allocator_alloc() doc