linux-kernel - linux-next: manual merge of the iommu tree with the dma-mapping 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: <20220502134624.76a88cff@canb.auug.org.au>
Date:   Mon, 2 May 2022 13:46:24 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Joerg Roedel <joro@...tes.org>, Christoph Hellwig <hch@....de>
Cc:     Joerg Roedel <jroedel@...e.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Mario Limonciello <mario.limonciello@....com>
Subject: linux-next: manual merge of the iommu tree with the dma-mapping
 tree

Hi all,

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

  drivers/iommu/amd/iommu.c

between commit:

  78013eaadf69 ("x86: remove the IOMMU table infrastructure")

from the dma-mapping tree and commit:

  121660bba631 ("iommu/amd: Enable swiotlb in all cases")

from the iommu tree.

I fixed it up (the latter removed the code modified by the former) 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

Content of type "application/pgp-signature" skipped