From f65a4354833ef94ecd37d86f2dfc29226ddd55c6 Mon Sep 17 00:00:00 2001
From: Adam Sawicki <adam.sawicki@amd.com>
Date: Wed, 6 Dec 2017 13:39:59 +0100
Subject: [PATCH] Fix in documentation.

---
 src/vk_mem_alloc.h | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/src/vk_mem_alloc.h b/src/vk_mem_alloc.h
index 7795762..b4565ad 100644
--- a/src/vk_mem_alloc.h
+++ b/src/vk_mem_alloc.h
@@ -739,12 +739,6 @@ typedef enum VmaAllocatorCreateFlagBits {
     - VK_KHR_get_memory_requirements2
     - VK_KHR_dedicated_allocation
 
-    If this flag is enabled, you must also provide
-    VmaAllocatorCreateInfo::pVulkanFunctions and fill at least members:
-    VmaVulkanFunctions::vkGetBufferMemoryRequirements2KHR,
-    VmaVulkanFunctions::vkGetImageMemoryRequirements2KHR, because they are never
-    imported statically.
-
 When this flag is set, you can experience following warnings reported by Vulkan
 validation layer. You can ignore them.