[PATCH] winevulkan: Fix some typos in comments.

Francois Gouget fgouget at free.fr
Thu Mar 15 12:12:08 CDT 2018


Signed-off-by: Francois Gouget <fgouget at free.fr>
---
 dlls/winevulkan/make_vulkan | 2 +-
 dlls/winevulkan/vk.xml      | 2 +-
 dlls/winevulkan/vulkan.c    | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/dlls/winevulkan/make_vulkan b/dlls/winevulkan/make_vulkan
index 5c5f38f40f1..1a2ae1700a9 100755
--- a/dlls/winevulkan/make_vulkan
+++ b/dlls/winevulkan/make_vulkan
@@ -450,7 +450,7 @@ class VkFunction(object):
         else:
             proto += " {0}(".format(self.name)
 
-        # Add all the paremeters.
+        # Add all the parameters.
         proto += ", ".join([p.definition() for p in self.params])
 
         if postfix is not None:
diff --git a/dlls/winevulkan/vk.xml b/dlls/winevulkan/vk.xml
index e013ce8b603..3f53dad504f 100644
--- a/dlls/winevulkan/vk.xml
+++ b/dlls/winevulkan/vk.xml
@@ -1308,7 +1308,7 @@ maintained in the master branch of the Khronos Vulkan GitHub project.
             <member><type>uint32_t</type>               <name>maxGeometryOutputVertices</name></member>         <!-- max number of vertices that can be emitted in geometry stage -->
             <member><type>uint32_t</type>               <name>maxGeometryTotalOutputComponents</name></member>  <!-- max total number of components (all vertices) written in geometry stage -->
                 <!-- fragment stage limits -->
-            <member><type>uint32_t</type>               <name>maxFragmentInputComponents</name></member>        <!-- max number of input compontents read in fragment stage -->
+            <member><type>uint32_t</type>               <name>maxFragmentInputComponents</name></member>        <!-- max number of input components read in fragment stage -->
             <member><type>uint32_t</type>               <name>maxFragmentOutputAttachments</name></member>      <!-- max number of output attachments written in fragment stage -->
             <member><type>uint32_t</type>               <name>maxFragmentDualSrcAttachments</name></member>     <!-- max number of output attachments written when using dual source blending -->
             <member><type>uint32_t</type>               <name>maxFragmentCombinedOutputResources</name></member><!-- max total number of storage buffers, storage images and output buffers -->
diff --git a/dlls/winevulkan/vulkan.c b/dlls/winevulkan/vulkan.c
index 0a5a77dcf3a..0daec103f2e 100644
--- a/dlls/winevulkan/vulkan.c
+++ b/dlls/winevulkan/vulkan.c
@@ -153,7 +153,7 @@ static VkResult wine_vk_instance_convert_create_info(const VkInstanceCreateInfo
     dst->pApplicationInfo = src->pApplicationInfo;
 
     /* Application and loader can pass in a chain of extensions through pNext.
-     * We can't blindy pass these through as often these contain callbacks or
+     * We can't blindly pass these through as often these contain callbacks or
      * they can even be pass structures for loader / ICD internal use. For now
      * we ignore everything in pNext chain, but we print FIXMEs.
      */
@@ -942,7 +942,7 @@ void * WINAPI wine_vk_icdGetInstanceProcAddr(VkInstance instance, const char *na
     TRACE("%p %s\n", instance, debugstr_a(name));
 
     /* Initial version of the Vulkan ICD spec required vkGetInstanceProcAddr to be
-     * exported. vk_icdGetInstanceProcAddr was added later to separete ICD calls from
+     * exported. vk_icdGetInstanceProcAddr was added later to separate ICD calls from
      * Vulkan API. One of them in our case should forward to the other, so just forward
      * to the older vkGetInstanceProcAddr.
      */
-- 
2.16.1



More information about the wine-devel mailing list