[RFC v2 2/3] dma-buf/fence-array: add fence_array_teardown()

2016-06-27 Thread Gustavo Padovan
From: Gustavo Padovan As the array of fence callbacks held by an active struct fence_array each has a reference to the struct fence_array, when the owner of the fence_array is freed it must dispose of the callback references before it can free the fence_array. This can not happen simply during fe

[RFC v2 2/3] dma-buf/fence-array: add fence_array_teardown()

2016-06-28 Thread Christian König
Am 27.06.2016 um 21:29 schrieb Gustavo Padovan: > From: Gustavo Padovan > > As the array of fence callbacks held by an active struct fence_array > each has a reference to the struct fence_array, when the owner of the > fence_array is freed it must dispose of the callback references before > it can

[RFC v2 2/3] dma-buf/fence-array: add fence_array_teardown()

2016-06-28 Thread Christian König
Am 28.06.2016 um 16:17 schrieb Gustavo Padovan: > 2016-06-28 Christian König : > >> Am 27.06.2016 um 21:29 schrieb Gustavo Padovan: >>> From: Gustavo Padovan >>> >>> As the array of fence callbacks held by an active struct fence_array >>> each has a reference to the struct fence_array, when the o

[RFC v2 2/3] dma-buf/fence-array: add fence_array_teardown()

2016-06-28 Thread Gustavo Padovan
2016-06-28 Christian König : > Am 27.06.2016 um 21:29 schrieb Gustavo Padovan: > > From: Gustavo Padovan > > > > As the array of fence callbacks held by an active struct fence_array > > each has a reference to the struct fence_array, when the owner of the > > fence_array is freed it must dispos

[RFC v2 2/3] dma-buf/fence-array: add fence_array_teardown()

2016-06-28 Thread Gustavo Padovan
2016-06-28 Christian König : > Am 28.06.2016 um 16:17 schrieb Gustavo Padovan: > > 2016-06-28 Christian König : > > > > > Am 27.06.2016 um 21:29 schrieb Gustavo Padovan: > > > > From: Gustavo Padovan > > > > > > > > As the array of fence callbacks held by an active struct fence_array > > > >