lkml.org 
[lkml]   [2021]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH for-next 1/3] dma-buf: Fix pin callback comment
From
Date
Am 12.10.21 um 14:09 schrieb Gal Pressman:
> 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 <galpress@amazon.com>

Reviewed-by: Christian König <christian.koenig@amd.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

\
 
 \ /
  Last update: 2021-10-18 15:01    [W:0.123 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site