From: Gal Pressman <galpress@amazon.com>
To: "Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Doug Ledford" <dledford@redhat.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>
Cc: <linux-media@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<linux-kernel@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
Oded Gabbay <ogabbay@habana.ai>, Tomer Tayar <ttayar@habana.ai>,
Yossi Leybovich <sleybo@amazon.com>,
Alexander Matushevsky <matua@amazon.com>,
Leon Romanovsky <leonro@nvidia.com>,
Jianxin Xiong <jianxin.xiong@intel.com>,
Firas Jahjah <firasj@amazon.com>,
Gal Pressman <galpress@amazon.com>
Subject: [PATCH for-next 1/3] dma-buf: Fix pin callback comment
Date: Tue, 12 Oct 2021 15:09:01 +0300 [thread overview]
Message-ID: <20211012120903.96933-2-galpress@amazon.com> (raw)
In-Reply-To: <20211012120903.96933-1-galpress@amazon.com>
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>
---
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
next prev parent reply other threads:[~2021-10-12 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 12:09 [PATCH for-next 0/3] EFA dmabuf memory regions Gal Pressman
2021-10-12 12:09 ` Gal Pressman [this message]
2021-10-18 12:59 ` [PATCH for-next 1/3] dma-buf: Fix pin callback comment Christian König
2021-10-12 12:09 ` [PATCH for-next 2/3] RDMA/umem: Allow pinned dmabuf umem usage Gal Pressman
2021-10-12 12:09 ` [PATCH for-next 3/3] RDMA/efa: Add support for dmabuf memory regions Gal Pressman
2021-10-26 6:10 ` [PATCH for-next 0/3] EFA " Gal Pressman
2021-10-27 14:52 ` Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211012120903.96933-2-galpress@amazon.com \
--to=galpress@amazon.com \
--cc=christian.koenig@amd.com \
--cc=dledford@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=firasj@amazon.com \
--cc=jgg@ziepe.ca \
--cc=jianxin.xiong@intel.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=ogabbay@habana.ai \
--cc=sleybo@amazon.com \
--cc=sumit.semwal@linaro.org \
--cc=ttayar@habana.ai \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).