From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>,
Sumit Semwal <sumit.semwal@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
DRI-devel <dri-devel@lists.freedesktop.org>,
Linux Media ML <linux-media@vger.kernel.org>
Subject: Re: [PATCH] dma-buf: Cleanup comments on dma_buf_map_attachment()
Date: Thu, 2 Nov 2017 10:45:57 +0100 [thread overview]
Message-ID: <118709d7-07f7-7d81-4861-6cbff81e5ba7@gmail.com> (raw)
In-Reply-To: <20171101140630.2884-1-Liviu.Dudau@arm.com>
Am 01.11.2017 um 15:06 schrieb Liviu Dudau:
> Mappings need to be unmapped by calling dma_buf_unmap_attachment() and
> not by calling again dma_buf_map_attachment(). Also fix some spelling
> mistakes.
>
> Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/dma-buf/dma-buf.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
> index bc1cb284111cb..1792385405f0e 100644
> --- a/drivers/dma-buf/dma-buf.c
> +++ b/drivers/dma-buf/dma-buf.c
> @@ -351,13 +351,13 @@ static inline int is_dma_buf_file(struct file *file)
> *
> * 2. Userspace passes this file-descriptors to all drivers it wants this buffer
> * to share with: First the filedescriptor is converted to a &dma_buf using
> - * dma_buf_get(). The the buffer is attached to the device using
> + * dma_buf_get(). Then the buffer is attached to the device using
> * dma_buf_attach().
> *
> * Up to this stage the exporter is still free to migrate or reallocate the
> * backing storage.
> *
> - * 3. Once the buffer is attached to all devices userspace can inniate DMA
> + * 3. Once the buffer is attached to all devices userspace can initiate DMA
> * access to the shared buffer. In the kernel this is done by calling
> * dma_buf_map_attachment() and dma_buf_unmap_attachment().
> *
> @@ -617,7 +617,7 @@ EXPORT_SYMBOL_GPL(dma_buf_detach);
> * Returns sg_table containing the scatterlist to be returned; returns ERR_PTR
> * on error. May return -EINTR if it is interrupted by a signal.
> *
> - * A mapping must be unmapped again using dma_buf_map_attachment(). Note that
> + * A mapping must be unmapped by using dma_buf_unmap_attachment(). Note that
> * the underlying backing storage is pinned for as long as a mapping exists,
> * therefore users/importers should not hold onto a mapping for undue amounts of
> * time.
next prev parent reply other threads:[~2017-11-02 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 14:06 [PATCH] dma-buf: Cleanup comments on dma_buf_map_attachment() Liviu Dudau
2017-11-02 4:01 ` Alex Deucher
2017-11-02 9:45 ` Christian König [this message]
2017-11-02 13:14 ` Gustavo Padovan
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=118709d7-07f7-7d81-4861-6cbff81e5ba7@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Liviu.Dudau@arm.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
/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).