From 65870346e412e905edfc4f5aa7bfc6b8cb02bb08 Mon Sep 17 00:00:00 2001
From: Camilla Berglund <elmindreda@elmindreda.org>
Date: Thu, 18 Feb 2016 15:16:03 +0100
Subject: [PATCH] Add Vulkan functions to thread safety section

---
 docs/intro.dox | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/intro.dox b/docs/intro.dox
index cb3bdbc9..a54bf96f 100644
--- a/docs/intro.dox
+++ b/docs/intro.dox
@@ -250,6 +250,15 @@ version related functions may be called from any thread:
  - @ref glfwGetVersion
  - @ref glfwGetVersionString
 
+Vulkan objects may be created and information queried from any thread.  The
+following Vulkan related functions may be called from any thread:
+
+ - @ref glfwVulkanSupported
+ - @ref glfwGetRequiredInstanceExtensions
+ - @ref glfwGetInstanceProcAddress
+ - @ref glfwGetPhysicalDevicePresentationSupport
+ - @ref glfwCreateWindowSurface
+
 GLFW uses no synchronization objects internally except for thread-local storage
 to keep track of the current context for each thread.  Synchronization is left
 to the application.