Commit 21bb9d64 authored by Christoph Hellwig's avatar Christoph Hellwig

swiotlb: remove a pointless comment

This comments describes an aspect of the map_sg interface that isn't
even exploited by swiotlb.
Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
Reviewed-by: default avatarRobin Murphy <robin.murphy@arm.com>
Reviewed-by: default avatarKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
parent b9fd0426
...@@ -925,12 +925,6 @@ swiotlb_sync_single_for_device(struct device *hwdev, dma_addr_t dev_addr, ...@@ -925,12 +925,6 @@ swiotlb_sync_single_for_device(struct device *hwdev, dma_addr_t dev_addr,
* appropriate dma address and length. They are obtained via * appropriate dma address and length. They are obtained via
* sg_dma_{address,length}(SG). * sg_dma_{address,length}(SG).
* *
* NOTE: An implementation may be able to use a smaller number of
* DMA address/length pairs than there are SG table elements.
* (for example via virtual mapping capabilities)
* The routine returns the number of addr/length pairs actually
* used, at most nents.
*
* Device ownership issues as mentioned above for swiotlb_map_page are the * Device ownership issues as mentioned above for swiotlb_map_page are the
* same here. * same here.
*/ */
......
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