commit a569a50e85d51b0dff1b16cfd2c64222f921b6da
author Courtney Goeltzenleuchter <courtney@LunarG.com> Wed Apr 29 17:16:21 2015 -0600
committer Courtney Goeltzenleuchter <courtney@LunarG.com> Fri May 01 17:26:57 2015 -0600
tree be493a25c19e0161ce0e74c1080138991e466df3
parent da4a99e924e8152a834a6ee41ed98f60e133438a

bug-13690: Clarification on vkFlushMappedMemory

Bug 13690 - Clarification on the behavior of vkFlushMappedMemory
svn ID: 30914 & 30888

vk-layer-generate.py

diff --git a/vk-layer-generate.py b/vk-layer-generate.py
index 680d3c4..326a47e 100755
--- a/vk-layer-generate.py
+++ b/vk-layer-generate.py
@@ -1170,7 +1170,7 @@
             using_line += '    // validate_memory_mapping_status(pMemRefs, memRefCount);\n'
             using_line += '    // validate_mem_ref_count(memRefCount);\n'
             using_line += '    loader_platform_thread_unlock_mutex(&objLock);\n'
-        elif 'MemoryRange' in proto.name:
+        elif 'QueueBindObjectMemoryRange' in proto.name or 'QueueBindImageMemoryRange' in proto.name:
             using_line = '    loader_platform_thread_lock_mutex(&objLock);\n'
             using_line += '    if (validateQueueFlags(queue) == VK_FALSE) {\n'
             using_line += '        char str[1024];\n'