On Wed, Jan 04, 2017 at 09:23:34PM +0530, Sumit Semwal wrote:
> Hi Chris,
>
> Thanks for your patches!
>
> On 4 January 2017 at 20:40, Daniel Vetter wrote:
> > On Wed, Jan 04, 2017 at 02:12:20PM +, Chris Wilson wrote:
> >> As the fence->status is an optional field that may be set before
>
Hi Chris,
Thanks for your patches!
On 4 January 2017 at 20:40, Daniel Vetter wrote:
> On Wed, Jan 04, 2017 at 02:12:20PM +, Chris Wilson wrote:
>> As the fence->status is an optional field that may be set before
>> dma_fence_signal() is called to convey that the fence completed with an
>>
On Wed, Jan 04, 2017 at 02:12:20PM +, Chris Wilson wrote:
> As the fence->status is an optional field that may be set before
> dma_fence_signal() is called to convey that the fence completed with an
> error, we have to ensure that it is always set to zero on initialisation
> so that the
As the fence->status is an optional field that may be set before
dma_fence_signal() is called to convey that the fence completed with an
error, we have to ensure that it is always set to zero on initialisation
so that the typical use (i.e. unset) always flags a successful completion.