From mboxrd@z Thu Jan 1 00:00:00 1970 From: konrad.wilk@oracle.com (Konrad Rzeszutek Wilk) Date: Thu, 18 Oct 2018 20:09:34 -0400 Subject: [PATCH 01/10] swiotlb: remove a pointless comment In-Reply-To: <20181008080246.20543-2-hch@lst.de> References: <20181008080246.20543-1-hch@lst.de> <20181008080246.20543-2-hch@lst.de> Message-ID: <20181019000934.GB1251@char.us.oracle.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Oct 08, 2018 at 10:02:37AM +0200, Christoph Hellwig wrote: > This comments describes an aspect of the map_sg interface that isn't > even exploited by swiotlb. > > Signed-off-by: Christoph Hellwig Reviewed-by: Konrad Rzeszutek Wilk Thank you! > --- > kernel/dma/swiotlb.c | 6 ------ > 1 file changed, 6 deletions(-) > > diff --git a/kernel/dma/swiotlb.c b/kernel/dma/swiotlb.c > index 4f8a6dbf0b60..9062b14bc7f4 100644 > --- a/kernel/dma/swiotlb.c > +++ b/kernel/dma/swiotlb.c > @@ -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 > * 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 > * same here. > */ > -- > 2.19.0 >