From: Jacob Pan <jacob.pan@linux.microsoft.com>
To: Yu Zhang <zhangyu1@linux.microsoft.com>
Cc: joro@8bytes.org, iommu@lists.linux.dev,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
lkp@intel.com, oe-kbuild-all@lists.linux.dev,
joerg.roedel@amd.com, jgg@nvidia.com, will@kernel.org,
robin.murphy@arm.com, mhklinux@outlook.com, wei.liu@kernel.org,
easwar.hariharan@linux.microsoft.com,
jacob.pan@linux.microsoft.com
Subject: Re: [PATCH 0/2] iommu/hyperv: Fix guest IOMMU build issues
Date: Thu, 15 Oct 2026 08:29:24 -0700 [thread overview]
Message-ID: <20261015082924.000009a0@linux.microsoft.com> (raw)
In-Reply-To: <20261015082351.184252-1-zhangyu1@linux.microsoft.com>
Hi Yu,
On Thu, 15 Oct 2026 16:23:49 +0800
Yu Zhang <zhangyu1@linux.microsoft.com> wrote:
> This series address two issues reported by kernel test robot in the
> recently applied Hyper-V guest IOMMU driver.
>
> The first one adds the missing PCI dependency to prevent a link
> failure when CONFIG_PCI is disabled. And the second makes
> hv_iommu_device static to address a sparse warning.
>
> The patches are based on the hyper-v branch of the IOMMU tree.
>
> Yu Zhang (2):
> iommu/hyperv: Add missing PCI dependency for the guest IOMMU driver
> iommu/hyperv: Make hv_iommu_device static
>
> drivers/iommu/hyperv/Kconfig | 2 +-
> drivers/iommu/hyperv/hv-iommu-guest.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
Reviewed-by: Jacob Pan <jacob.pan@linux.microsoft.com>
next prev parent reply other threads:[~2026-10-15 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 8:23 [PATCH 0/2] iommu/hyperv: Fix guest IOMMU build issues Yu Zhang
2026-10-15 8:23 ` [PATCH 1/2] iommu/hyperv: Add missing PCI dependency for the guest IOMMU driver Yu Zhang
2026-10-15 8:23 ` [PATCH 2/2] iommu/hyperv: Make hv_iommu_device static Yu Zhang
2026-10-15 12:36 ` [PATCH 0/2] iommu/hyperv: Fix guest IOMMU build issues Jason Gunthorpe
2026-10-15 15:29 ` Jacob Pan [this message]
2026-10-15 15:52 ` Jörg Rödel
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=20261015082924.000009a0@linux.microsoft.com \
--to=jacob.pan@linux.microsoft.com \
--cc=easwar.hariharan@linux.microsoft.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mhklinux@outlook.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=wei.liu@kernel.org \
--cc=will@kernel.org \
--cc=zhangyu1@linux.microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox