Jesse Hall d58c304cc6 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		2012-06-28 17:08:42 -07:00
..
binder	Aligning native Parcel implementation to Java.	2012-06-08 08:29:01 -07:00
cpustats
gui	Clarify aborted updateTexImage use of fences	2012-06-28 17:08:42 -07:00
ui	Return fence to client in dequeuBuffer	2012-06-28 17:08:42 -07:00
utils