Skip to content

Commit 36b21cb

Browse files
committed
docs(cuda.core): let "must" govern both verbs in the config entry
The config entry said config "must name the resource's location_type, handle_type, and numa_id and passes the same checks as the constructor". Make it "pass", so both parts read as requirements. Signed-off-by: Som Tripathi <[email protected]>
1 parent 785fd3d commit 36b21cb

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

‎cuda_core/cuda/core/_memory/_virtual_memory_resource.pyi‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -282,7 +282,7 @@ class VirtualMemoryResource(MemoryResource):
282282
Configuration for the new physical memory chunk only. Existing
283283
chunks keep the access they were created with, and the resource's
284284
own configuration is unchanged. It must name the resource's
285-
``location_type``, ``handle_type``, and ``numa_id`` and passes the
285+
``location_type``, ``handle_type``, and ``numa_id`` and pass the
286286
same checks as the constructor.
287287
When ``buf`` already covers ``new_size`` there is no new chunk, so
288288
``config`` has no effect. This method never changes the access of

‎cuda_core/cuda/core/_memory/_virtual_memory_resource.pyx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -728,7 +728,7 @@ cdef class VirtualMemoryResource(MemoryResource):
728728
Configuration for the new physical memory chunk only. Existing
729729
chunks keep the access they were created with, and the resource's
730730
own configuration is unchanged. It must name the resource's
731-
``location_type``, ``handle_type``, and ``numa_id`` and passes the
731+
``location_type``, ``handle_type``, and ``numa_id`` and pass the
732732
same checks as the constructor.
733733
When ``buf`` already covers ``new_size`` there is no new chunk, so
734734
``config`` has no effect. This method never changes the access of

0 commit comments

Comments
 (0)