dma-buf: Fix pin callback comment
authorGal Pressman <galpress@amazon.com>
Tue, 12 Oct 2021 12:09:01 +0000 (15:09 +0300)
committerJason Gunthorpe <jgg@nvidia.com>
Wed, 27 Oct 2021 14:28:20 +0000 (11:28 -0300)
The pin callback does not necessarily have to move the memory to system
memory, remove the sentence from the comment.

Link: https://lore.kernel.org/r/20211012120903.96933-2-galpress@amazon.com
Signed-off-by: Gal Pressman <galpress@amazon.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
include/linux/dma-buf.h

index 8b32b4b..8afe182 100644 (file)
@@ -86,8 +86,8 @@ struct dma_buf_ops {
         * @pin:
         *
         * This is called by dma_buf_pin() and lets the exporter know that the
-        * DMA-buf can't be moved any more. The exporter should pin the buffer
-        * into system memory to make sure it is generally accessible by other
+        * DMA-buf can't be moved any more. Ideally, the exporter should
+        * pin the buffer so that it is generally accessible by all
         * devices.
         *
         * This is called with the &dmabuf.resv object locked and is mutual