[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20220307125036.5aeaabc8@canb.auug.org.au>
Date: Mon, 7 Mar 2022 12:50:36 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Joerg Roedel <joro@...tes.org>
Cc: Borislav Petkov <bp@...e.de>, Fenghua Yu <fenghua.yu@...el.com>,
Joerg Roedel <jroedel@...e.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Lu Baolu <baolu.lu@...ux.intel.com>
Subject: linux-next: manual merge of the tip tree with the iommu tree
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
drivers/iommu/intel/iommu.c
between commit:
241469685d8d ("iommu/vt-d: Remove aux-domain related callbacks")
from the iommu tree and commit:
701fac40384f ("iommu/sva: Assign a PASID to mm on PASID allocation and free it on mm exit")
from the tip tree.
I fixed it up (I used the former since it removed the functions modified
by the latter) 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
Powered by blists - more mailing lists