Hi Linus,

The following changes since commit 5ffde2f67181195d457b95df44b8f88e8d969d89:

  Merge branches 'arm/rockchip', 'arm/exynos', 'arm/smmu', 'x86/vt-d', 
'x86/amd', 'default-domains' and 'core' into next (2015-06-19 17:17:47 +0200)

are available in the git repository at:


  git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git 
tags/iommu-fixes-v4.2

for you to fetch changes up to 7a5a566eab48da7522f601f96aef3af102178046:

  iommu/amd: Introduce protection_domain_init() function (2015-07-01 08:43:07 
+0200)

----------------------------------------------------------------
IOMMU Fixes for Linux v4.2-rc0

Four fixes have queued up to fix regressions introduced after v4.1:

        * Don't fail IOMMU driver initialization when the add_device
          call-back returns -ENODEV, as that just means that the device
          is not translated by the IOMMU. This is pretty common on ARM.

        * Two fixes for the ARM-SMMU driver for a wrong feature check
          and to remove a redundant NULL check.

        * A fix for the AMD IOMMU driver to fix a boot panic on systems
          where the BIOS requests Unity Mappings in the IVRS table.

----------------------------------------------------------------
Joerg Roedel (2):
      iommu: Ignore -ENODEV errors from add_device call-back
      iommu/amd: Introduce protection_domain_init() function

Markus Elfring (1):
      iommu/arm-smmu: Delete an unnecessary check before the function call 
"free_io_pgtable_ops"

Will Deacon (1):
      iommu/arm-smmu: Fix broken ATOS check

 drivers/iommu/amd_iommu.c   | 26 ++++++++++++++++----------
 drivers/iommu/arm-smmu-v3.c |  3 +--
 drivers/iommu/arm-smmu.c    |  2 +-
 drivers/iommu/iommu.c       | 13 ++++++++++++-
 4 files changed, 30 insertions(+), 14 deletions(-)

Please pull.

Thanks,

        Joerg

Attachment: signature.asc
Description: Digital signature

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

Reply via email to