On 23/05/2019 08:00, Christoph Hellwig wrote:

Hi Robin and Joerg,

I think we are finally ready for the generic dma-iommu series.  I have
various DMA API changes pending, and Tom has patches ready to convert
the AMD and Intel iommu drivers over to it.  I'd love to have this
in a stable branch shared between the dma-mapping and iommu trees
the day after rc2 is released.  I volunteer to create the branch,
but I'm fine with it living in the iommu tree as well.

Yup, I'd also like to see this in -next ASAP in the hope that board farms and maybe even real users can start chewing on it. Thanks for persevering :)

Robin.



A git tree is also available at:

     git://git.infradead.org/users/hch/misc.git dma-iommu-ops.6

Gitweb:

     
http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-iommu-ops.6

Changes since v5:
  - rebased to latest linus tree and dropped a patch now merged
  - remove the now pointless __dma_iommu_mmap function
  - restore a cleanup from Robin that would have caused a conflict in
    last merge winow, but is fine now

Changes since v4:
  - rebased to 5.2-rc1

Changes since v3:
  - fold the separate patch to refactor mmap bounds checking
  - don't warn on not finding a vm_area
  - improve a commit log
  - refactor __dma_iommu_free a little differently
  - remove a minor MSI map cleanup to avoid a conflict with the
    "Split iommu_dma_map_msi_msg" series

Changes since v2:
  - address various review comments and include patches from Robin

Changes since v1:
  - only include other headers in dma-iommu.h if CONFIG_DMA_IOMMU is enabled
  - keep using a scatterlist in iommu_dma_alloc
  - split out mmap/sgtable fixes and move them early in the series
  - updated a few commit logs
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

Reply via email to