[SRU][jammy][PATCH 1/6] dma-buf: Fix pin callback comment

[Ian May]

From: Gal Pressman <galpress at amazon.com>

Buglink: https://bugs.launchpad.net/bugs/2040526

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 at amazon.com>
Reviewed-by: Christian König <christian.koenig at amd.com>
Signed-off-by: Jason Gunthorpe <jgg at nvidia.com>
(cherry picked from commit 5460601de590158b37619f8e18b678aa18da6345)
Signed-off-by: Tushar Dave <tdave at nvidia.com>
Signed-off-by: Ian May <ian.may at canonical.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 3ad636a13b8e..f6344578e0da 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.25.1