Commit 5460601d authored by Gal Pressman's avatar Gal Pressman Committed by Jason Gunthorpe

dma-buf: Fix pin callback comment

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.comSigned-off-by: default avatarGal Pressman <galpress@amazon.com>
Reviewed-by: default avatarChristian König <christian.koenig@amd.com>
Signed-off-by: default avatarJason Gunthorpe <jgg@nvidia.com>
parent e058953c
...@@ -86,8 +86,8 @@ struct dma_buf_ops { ...@@ -86,8 +86,8 @@ struct dma_buf_ops {
* @pin: * @pin:
* *
* This is called by dma_buf_pin() and lets the exporter know that the * 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 * DMA-buf can't be moved any more. Ideally, the exporter should
* into system memory to make sure it is generally accessible by other * pin the buffer so that it is generally accessible by all
* devices. * devices.
* *
* This is called with the &dmabuf.resv object locked and is mutual * This is called with the &dmabuf.resv object locked and is mutual
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment