tree 30ff2d25f110e5cc78ea12bb384eb0c0d7a04a9f
parent f9783af225aa3b41ec0af36f90941a714269abb7
author Jesse Hall <jessehall@google.com> 1340921213 -0700
committer Jesse Hall <jessehall@google.com> 1340928522 -0700

Clarify aborted updateTexImage use of fences

When updateTexImage acquires a buffer but then aborts (due to an error
or the buffer being rejected), it releases the newly-acquired buffer.
It was passing the buffer slot's fences to releaseBuffer, even though
they hadn't been created after the acquire yet. This wasn't a bug,
since the fences would be cleared just after the buffer slot was last
released, but explicitly passing null fences makes this clearer.

Change-Id: I087f2ec3fd02c40f57782c1fca24eb9567e2943d