exo: Implement zcr_linux_explicit_synchronization_v1

third_party/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml

Index: third_party/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml
diff --git a/third_party/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml b/third_party/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml
index 16494ec84b109f61a80cb99870fb6f919640b016..34312adf38d3d4132cd008fc82b0dda004d64bf1 100644
--- a/third_party/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml
+++ b/third_party/wayland-protocols/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml
@@ -77,6 +77,11 @@
       </description>
     </request>
 
+    <enum name="error">

[reveman, 2016/10/12 19:20:20]

I included this in https://codereview.chromium.org/2397843002 so it should no
longer be needed after a rebase.

+      <entry name="invalid_fence" value="0"
+             summary="the fence specified by the client could not be imported"/>
+    </enum>
+
     <request name="set_acquire_fence">
       <description summary="set the acquire fence">
 	Set the acquire fence that must be signaled before the compositor
@@ -84,6 +89,9 @@
 
 	The acquire state is double-buffered state, and will be applied on
 	the next wl_surface.commit.
+
+	If the fence could not be imported, an INVALID_FENCE error is signaled
+	to the client.
       </description>
       <arg name="fd" type="fd" summary="fence fd"/>
     </request>