The pin callback does not necessarily have to move the memory to system
memory, remove the sentence from the comment.

Signed-off-by: Gal Pressman <galpr...@amazon.com>
---
 include/linux/dma-buf.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/linux/dma-buf.h b/include/linux/dma-buf.h
index efdc56b9d95f..225e09caeb98 100644
--- a/include/linux/dma-buf.h
+++ b/include/linux/dma-buf.h
@@ -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
-- 
2.33.0

Reply via email to