All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Eric Auger <eric.auger@redhat.com>, <kvm@vger.kernel.org>,
	Russell King <linux@armlinux.org.uk>
Subject: [PATCH 0/3] Tidy some parts of the VFIO kconfig world
Date: Tue, 23 Feb 2021 15:17:45 -0400	[thread overview]
Message-ID: <0-v1-df057e0f92c3+91-vfio_arm_compile_test_jgg@nvidia.com> (raw)

The main goal here is to add enough COMPILE_TEST that an ARM cross
compiler is not needed to be able to get compile coverage on VFIO. A
normal x86 compiler with COMPILE_TEST will do the job.

s390 and ppc are still needed, and I'm looking to see if any of that is
reasonable to change too.

Thanks,
Jason

Jason Gunthorpe (3):
  vfio: IOMMU_API should be selected
  vfio-platform: Add COMPILE_TEST to VFIO_PLATFORM
  ARM: amba: Allow some ARM_AMBA users to compile with COMPILE_TEST

 drivers/vfio/Kconfig          |  2 +-
 drivers/vfio/platform/Kconfig |  4 ++--
 include/linux/amba/bus.h      | 11 +++++++++++
 3 files changed, 14 insertions(+), 3 deletions(-)

-- 
2.30.0


             reply	other threads:[~2021-02-23 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 19:17 Jason Gunthorpe [this message]
2021-02-23 19:17 ` [PATCH 1/3] vfio: IOMMU_API should be selected Jason Gunthorpe
2021-02-24  9:50   ` Auger Eric
2021-03-03 12:36   ` Cornelia Huck
2021-03-03 12:52     ` Jason Gunthorpe
2021-02-23 19:17 ` [PATCH 2/3] vfio-platform: Add COMPILE_TEST to VFIO_PLATFORM Jason Gunthorpe
2021-02-24  9:42   ` Auger Eric
2021-02-24 13:00     ` Jason Gunthorpe
2021-02-23 19:17 ` [PATCH 3/3] ARM: amba: Allow some ARM_AMBA users to compile with COMPILE_TEST Jason Gunthorpe
2021-02-24  9:49   ` Auger Eric

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=0-v1-df057e0f92c3+91-vfio_arm_compile_test_jgg@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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.