From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat, 12 Jan 2019 18:52:40 +0000 (-0800)
Subject: Merge tag 'remove-dma_zalloc_coherent-5.0' of git://git.infradead.org/users/hch/dma... 
X-Git-Tag: v5.15~7180
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=66c56cfa64d9dbb9efa8a06c1aece77e8d57ea19;p=platform%2Fkernel%2Flinux-starfive.git

Merge tag 'remove-dma_zalloc_coherent-5.0' of git://git.infradead.org/users/hch/dma-mapping

Pull dma_zalloc_coherent() removal from Christoph Hellwig:
 "We've always had a weird situation around dma_zalloc_coherent. To
  safely support mapping the allocations to userspace major
  architectures like x86 and arm have always zeroed allocations from
  dma_alloc_coherent, but a couple other architectures were missing that
  zeroing either always or in corner cases.

  Then later we grew anothe dma_zalloc_coherent interface to explicitly
  request zeroing, but that just added __GFP_ZERO to the allocation
  flags, which for some allocators that didn't end up using the page
  allocator ended up being a no-op and still not zeroing the
  allocations.

  So for this merge window I fixed up all remaining architectures to
  zero the memory in dma_alloc_coherent, and made dma_zalloc_coherent a
  no-op wrapper around dma_alloc_coherent, which fixes all of the above
  issues.

  dma_zalloc_coherent is now pointless and can go away, and Luis helped
  me writing a cocchinelle script and patch series to kill it, which I
  think we should apply now just after -rc1 to finally settle these
  issue"

* tag 'remove-dma_zalloc_coherent-5.0' of git://git.infradead.org/users/hch/dma-mapping:
  dma-mapping: remove dma_zalloc_coherent()
  cross-tree: phase out dma_zalloc_coherent() on headers
  cross-tree: phase out dma_zalloc_coherent()
---

66c56cfa64d9dbb9efa8a06c1aece77e8d57ea19