linux-explicit-synchronization: Clarify implicit synchronization guar…

…antees of release events

Clarify that after zwp_buffer_release_v1 events, otherwise unused
buffers can be reused without any additional implicit synchronization.
This is in contrast to wl_buffer.release, which doesn't guarantee that
implicit synchronization is not required to safely use a buffer after
the event is received.

Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com>
Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.com>

unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml

@@ -226,6 +226,11 @@
         signaled when all operations by the compositor on that buffer for that
         commit have finished.
 
+        Once the fence has signaled, and assuming the associated buffer is not
+        pending release from other wl_surface.commit requests, no additional
+        explicit or implicit synchronization is required to safely reuse or
+        destroy the buffer.
+
         This event destroys the zwp_linux_buffer_release_v1 object.
       </description>
       <arg name="fence" type="fd" summary="fence for last operation on buffer"/>
@@ -238,6 +243,11 @@
         using it, or has a guarantee that all its operations on that buffer for
         that commit have finished.
 
+        Once this event is received, and assuming the associated buffer is not
+        pending release from other wl_surface.commit requests, no additional
+        explicit or implicit synchronization is required to safely reuse or
+        destroy the buffer.
+
         This event destroys the zwp_linux_buffer_release_v1 object.
       </description>
     </event>