From 0bbfaafce1c418fe63b55de8c82671f61fbb4e39 Mon Sep 17 00:00:00 2001 From: Dennis Hamester Date: Wed, 10 May 2017 20:02:28 +0200 Subject: [PATCH] Fix references to VK_ERROR_DEVICE_LOST It was mistakenly called VK_DEVICE_LOST. --- doc/specs/vulkan/chapters/synchronization.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/specs/vulkan/chapters/synchronization.txt b/doc/specs/vulkan/chapters/synchronization.txt index 71181a58..adfa1dc1 100644 --- a/doc/specs/vulkan/chapters/synchronization.txt +++ b/doc/specs/vulkan/chapters/synchronization.txt @@ -973,7 +973,7 @@ with the following return codes: | Status | Meaning | ename:VK_SUCCESS | The fence specified by pname:fence is signaled. | ename:VK_NOT_READY | The fence specified by pname:fence is unsignaled. -| ename:VK_DEVICE_LOST | The device has been lost. See <>. +| ename:VK_ERROR_DEVICE_LOST | The device has been lost. See <>. |==== If a <> command is pending @@ -983,7 +983,7 @@ of date. If the device has been lost (see <>), fname:vkGetFenceStatus may: return any of the above status codes. If the device has been lost and fname:vkGetFenceStatus is called repeatedly, -it will eventually return either ename:VK_SUCCESS or ename:VK_DEVICE_LOST. +it will eventually return either ename:VK_SUCCESS or ename:VK_ERROR_DEVICE_LOST. include::../validity/protos/vkGetFenceStatus.txt[] @@ -1079,7 +1079,7 @@ fname:vkWaitForFences returns ename:VK_SUCCESS. If device loss occurs (see <>) before the timeout has expired, fname:vkWaitForFences must: return in finite time -with either ename:VK_SUCCESS or ename:VK_DEVICE_LOST. +with either ename:VK_SUCCESS or ename:VK_ERROR_DEVICE_LOST. .Note [NOTE]