dma-buf: Cleanup comments on dma_buf_map_attachment() (c138782d) · Commits · 戴 / test

drivers/dma-buf/dma-buf.c

+3 −3

Original line number	Diff line number	Diff line
		@@ -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.