All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jason Gunthorpe <jgg@nvidia.com>,
	Alex Williamson <alex.williamson@redhat.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Yi Liu <yi.l.liu@intel.com>
Subject: linux-next: manual merge of the iommufd tree with the vfio tree
Date: Tue, 6 Dec 2022 12:55:42 +1100	[thread overview]
Message-ID: <20221206125542.52ea97a7@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 2296 bytes --]

Hi all,

Today's linux-next merge of the iommufd tree got conflicts in:

  drivers/vfio/Kconfig
  drivers/vfio/Makefile

between commits:

  20601c45a0fa ("vfio: Remove CONFIG_VFIO_SPAPR_EEH")
  e2d55709398e ("vfio: Fold vfio_virqfd.ko into vfio.ko")

from the vfio tree and commits:

  a4d1f91db502 ("vfio-iommufd: Support iommufd for physical VFIO devices")
  e5a9ec7e096a ("vfio: Make vfio_container optionally compiled")
  c2849d718d26 ("vfio: Move vfio group specific code into group.c")

from the iommufd 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/vfio/Kconfig
index 0b8d53f63c7e,286c1663bd75..000000000000
--- a/drivers/vfio/Kconfig
+++ b/drivers/vfio/Kconfig
@@@ -38,6 -46,17 +46,12 @@@ config VFIO_NOIOMM
  	  this mode since there is no IOMMU to provide DMA translation.
  
  	  If you don't know what to do here, say N.
+ endif
+ 
 -config VFIO_SPAPR_EEH
 -	tristate
 -	depends on EEH && VFIO_IOMMU_SPAPR_TCE
 -	default VFIO
 -
+ config VFIO_VIRQFD
 -	tristate
++	bool
+ 	select EVENTFD
+ 	default n
  
  source "drivers/vfio/pci/Kconfig"
  source "drivers/vfio/platform/Kconfig"
diff --cc drivers/vfio/Makefile
index 0721ed4831c9,3783db7e8082..000000000000
--- a/drivers/vfio/Makefile
+++ b/drivers/vfio/Makefile
@@@ -2,12 -2,17 +2,14 @@@
  obj-$(CONFIG_VFIO) += vfio.o
  
  vfio-y += vfio_main.o \
- 	  iova_bitmap.o \
- 	  container.o
+ 	  group.o \
+ 	  iova_bitmap.o
 +vfio-$(CONFIG_VFIO_VIRQFD) += virqfd.o
+ vfio-$(CONFIG_IOMMUFD) += iommufd.o
+ vfio-$(CONFIG_VFIO_CONTAINER) += container.o
  
 -obj-$(CONFIG_VFIO_VIRQFD) += vfio_virqfd.o
  obj-$(CONFIG_VFIO_IOMMU_TYPE1) += vfio_iommu_type1.o
  obj-$(CONFIG_VFIO_IOMMU_SPAPR_TCE) += vfio_iommu_spapr_tce.o
 -obj-$(CONFIG_VFIO_SPAPR_EEH) += vfio_spapr_eeh.o
  obj-$(CONFIG_VFIO_PCI) += pci/
  obj-$(CONFIG_VFIO_PLATFORM) += platform/
  obj-$(CONFIG_VFIO_MDEV) += mdev/

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-12-06  1:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  1:55 Stephen Rothwell [this message]
2022-12-06 23:23 ` linux-next: manual merge of the iommufd tree with the vfio tree Alex Williamson
2022-12-06 23:35 ` Jason Gunthorpe
2022-12-14 23:51 ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221206125542.52ea97a7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alex.williamson@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=yi.l.liu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.