From mboxrd@z Thu Jan 1 00:00:00 1970 From: catalin.marinas@arm.com (Catalin Marinas) Date: Fri, 12 Oct 2018 18:04:12 +0100 Subject: [PATCH 04/10] swiotlb: remove the overflow buffer In-Reply-To: <20181008080246.20543-5-hch@lst.de> References: <20181008080246.20543-1-hch@lst.de> <20181008080246.20543-5-hch@lst.de> Message-ID: <20181012170411.GB60150@arrakis.emea.arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Oct 08, 2018 at 10:02:40AM +0200, Christoph Hellwig wrote: > Like all other dma mapping drivers just return an error code instead > of an actual memory buffer. The reason for the overflow buffer was > that at the time swiotlb was invented there was no way to check for > dma mapping errors, but this has long been fixed. > > Signed-off-by: Christoph Hellwig > --- > arch/arm64/mm/dma-mapping.c | 2 +- > arch/powerpc/kernel/dma-swiotlb.c | 4 +-- > include/linux/dma-direct.h | 2 ++ > include/linux/swiotlb.h | 3 -- > kernel/dma/direct.c | 2 -- > kernel/dma/swiotlb.c | 59 ++----------------------------- > 6 files changed, 8 insertions(+), 64 deletions(-) I went through the patches and they look fine to me (with the vunmap fix for the last patch). For the arm64 bits: Acked-by: Catalin Marinas