bug-13690: Clarification on vkFlushMappedMemory

Bug 13690 - Clarification on the behavior of vkFlushMappedMemory
svn ID: 30914 & 30888
diff --git a/icd/nulldrv/nulldrv.c b/icd/nulldrv/nulldrv.c
index 2788c78..69c26c2 100644
--- a/icd/nulldrv/nulldrv.c
+++ b/icd/nulldrv/nulldrv.c
@@ -1731,11 +1731,19 @@
     return VK_SUCCESS;
 }
 
-ICD_EXPORT VkResult VKAPI vkFlushMappedMemory(
+ICD_EXPORT VkResult VKAPI vkFlushMappedMemoryRanges(
     VkDevice                                  device,
-    VkDeviceMemory                            mem_,
-    VkDeviceSize                              offset,
-    VkDeviceSize                              size)
+    uint32_t                                  memRangeCount,
+    const VkMappedMemoryRange*                pMemRanges)
+{
+    NULLDRV_LOG_FUNC;
+    return VK_SUCCESS;
+}
+
+ICD_EXPORT VkResult VKAPI vkInvalidateMappedMemoryRanges(
+    VkDevice                                  device,
+    uint32_t                                  memRangeCount,
+    const VkMappedMemoryRange*                pMemRanges)
 {
     NULLDRV_LOG_FUNC;
     return VK_SUCCESS;