From 73c8a017f81f8a6d162ee5e5865ad8a88eb3a052 Mon Sep 17 00:00:00 2001 From: Nikhil Joshi Date: Thu, 27 Jun 2024 10:55:35 +0530 Subject: [PATCH] Address left-over comments (#1194) Address some of the comments that were left out in earlier update. --- api/opencl_runtime_layer.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/api/opencl_runtime_layer.asciidoc b/api/opencl_runtime_layer.asciidoc index d18452d8..0e02f39c 100644 --- a/api/opencl_runtime_layer.asciidoc +++ b/api/opencl_runtime_layer.asciidoc @@ -5438,7 +5438,7 @@ The following restrictions shall apply - {clCreateImageWithProperties}. If {CL_MEM_DEVICE_HANDLE_LIST_KHR} was not specified, the acquire can be performed on a command-queue associated with any device in the context. - * The memory object will be acquired on all devices specified + * The memory object will be acquired for all devices specified via {CL_MEM_DEVICE_HANDLE_LIST_KHR} when the memory object was imported using {clCreateBufferWithProperties} or {clCreateImageWithProperties}. If {CL_MEM_DEVICE_HANDLE_LIST_KHR} was not specified, the memory object @@ -5531,7 +5531,7 @@ The following restrictions shall apply - {clCreateImageWithProperties}. If {CL_MEM_DEVICE_HANDLE_LIST_KHR} was not specified, the release can be performed on a command-queue associated with any device in the context. - * The memory object will be released on all devices specified via + * The memory object will be released for all devices specified via {CL_MEM_DEVICE_HANDLE_LIST_KHR} when the memory object was imported using {clCreateBufferWithProperties} or {clCreateImageWithProperties}. If {CL_MEM_DEVICE_HANDLE_LIST_KHR} was not specified, the memory object