From 8498e4c10dd1a6c0d1f3b6b82de439fc5e56aa29 Mon Sep 17 00:00:00 2001
From: Tadeo Kondrak <me@tadeo.ca>
Date: Thu, 11 Jun 2020 14:22:55 -0600
Subject: linux-explicit-synchronization: Annotate destructor events

Signed-off-by: Tadeo Kondrak <me@tadeo.ca>
---
 .../linux-explicit-synchronization-unstable-v1.xml                    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'unstable')

diff --git a/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml b/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml
index d0a8cf0..ac91641 100644
--- a/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml
+++ b/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml
@@ -219,7 +219,7 @@
       'immediate_release' event it is automatically destroyed.
     </description>
 
-    <event name="fenced_release">
+    <event name="fenced_release" type="destructor">
       <description summary="release buffer with fence">
         Sent when the compositor has finalised its usage of the associated
         buffer for the relevant commit, providing a dma_fence which will be
@@ -236,7 +236,7 @@
       <arg name="fence" type="fd" summary="fence for last operation on buffer"/>
     </event>
 
-    <event name="immediate_release">
+    <event name="immediate_release" type="destructor">
       <description summary="release buffer immediately">
         Sent when the compositor has finalised its usage of the associated
         buffer for the relevant commit, and either performed no operations
-- 
cgit v1.2.3