[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <72c45b14-f0c0-9d1c-0953-eea70ce513a0@kernel.org>
Date: Mon, 15 Jul 2019 00:17:27 -0400
From: Sinan Kaya <Okaya@...nel.org>
To: Fuqian Huang <huangfq.daxian@...il.com>
Cc: Andy Gross <agross@...nel.org>,
David Brown <david.brown@...aro.org>,
Vinod Koul <vkoul@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
linux-arm-msm@...r.kernel.org, dmaengine@...r.kernel.org,
linux-kernel@...r.kernel.org, Robin Murphy <robin.murphy@....com>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH v3 04/24] dmaengine: qcom_hidma: Remove call to memset
after dmam_alloc_coherent
On 7/14/2019 11:17 PM, Fuqian Huang wrote:
> In commit 518a2f1925c3
> ("dma-mapping: zero memory returned from dma_alloc_*"),
> dma_alloc_coherent has already zeroed the memory.
> So memset is not needed.
>
> Signed-off-by: Fuqian Huang <huangfq.daxian@...il.com>
I don't see SWIO or ARM64 IOMMU drivers getting impacted by
the mentioned change above (518a2f1925c3).
arch/alpha/kernel/pci_iommu.c | 2 +-
arch/arc/mm/dma.c | 2 +-
arch/c6x/mm/dma-coherent.c | 5 ++++-
arch/m68k/kernel/dma.c | 2 +-
arch/microblaze/mm/consistent.c | 2 +-
arch/openrisc/kernel/dma.c | 2 +-
arch/parisc/kernel/pci-dma.c | 4 ++--
arch/s390/pci/pci_dma.c | 2 +-
arch/sparc/kernel/ioport.c | 2 +-
arch/sparc/mm/io-unit.c | 2 +-
arch/sparc/mm/iommu.c | 2 +-
arch/xtensa/kernel/pci-dma.c | 2 +-
drivers/misc/mic/host/mic_boot.c | 2 +-
kernel/dma/virt.c | 2 +-
14 files changed, 18 insertions(+), 15 deletions(-)
How does this new behavior apply globally?
Powered by blists - more mailing lists