linux-kernel - linux-next: manual merge of the iommu tree with the asm-generic tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20231003120410.3c408680@canb.auug.org.au>
Date:   Tue, 3 Oct 2023 12:04:10 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Joerg Roedel <joro@...tes.org>, Arnd Bergmann <arnd@...db.de>
Cc:     Ard Biesheuvel <ardb@...nel.org>, Joerg Roedel <jroedel@...e.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Niklas Schnelle <schnelle@...ux.ibm.com>
Subject: linux-next: manual merge of the iommu tree with the asm-generic
 tree

Hi all,

Today's linux-next merge of the iommu tree got a conflict in:

  drivers/iommu/Kconfig

between commit:

  cf8e8658100d ("arch: Remove Itanium (IA-64) architecture")

from the asm-generic tree and commit:

  c76c067e488c ("s390/pci: Use dma-iommu layer")

from the iommu tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/iommu/Kconfig
index 7f04491ca5f0,3199fd54b462..000000000000
--- a/drivers/iommu/Kconfig
+++ b/drivers/iommu/Kconfig
@@@ -91,7 -91,7 +91,7 @@@ config IOMMU_DEBUGF
  choice
  	prompt "IOMMU default domain type"
  	depends on IOMMU_API
- 	default IOMMU_DEFAULT_DMA_LAZY if X86
 -	default IOMMU_DEFAULT_DMA_LAZY if X86 || IA64 || S390
++	default IOMMU_DEFAULT_DMA_LAZY if X86 || S390
  	default IOMMU_DEFAULT_DMA_STRICT
  	help
  	  Choose the type of IOMMU domain used to manage DMA API usage by
@@@ -146,7 -146,7 +146,7 @@@ config OF_IOMM
  
  # IOMMU-agnostic DMA-mapping layer
  config IOMMU_DMA
- 	def_bool ARM64 || X86
 -	def_bool ARM64 || IA64 || X86 || S390
++	def_bool ARM64 || X86 || S390
  	select DMA_OPS
  	select IOMMU_API
  	select IOMMU_IOVA

Content of type "application/pgp-signature" skipped