From: Wei Liu <wei.liu@kernel.org>
To: Jacob Pan <jacob.pan@linux.microsoft.com>
Cc: Mukesh R <mrathor@linux.microsoft.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
mhklinux@outlook.com, wei.liu@kernel.org,
zhangyu1@linux.microsoft.com, schakrabarti@linux.microsoft.com
Subject: Re: [PATCH V2] iommu/hyperv: Create hyperv subdirectory under drivers/iommu
Date: Sun, 7 Jun 2026 22:58:24 -0700 [thread overview]
Message-ID: <20260608055824.GA1555293@liuwe-devbox-debian-v2.local> (raw)
In-Reply-To: <20260603165604.00006e9f@linux.microsoft.com>
On Wed, Jun 03, 2026 at 04:56:04PM -0700, Jacob Pan wrote:
> Hi Mukesh,
>
> On Wed, 3 Jun 2026 15:50:10 -0700
> Mukesh R <mrathor@linux.microsoft.com> wrote:
>
> > Create hyperv subdirectory under drivers/iommu in anticipation of more
> > hyperv related files from upcoming PCI passthru and pv-IOMMU patches.
> > Also, the current file hyperv-iommu.c actually implements irq
> > remapping on x86, so rename to more appropriate hv-irq-remap-x86.c
> > and move it under the new hyperv subdirectory. Since this file
> > implements irq_remap_ops exposed by drivers/iommu/irq_remapping.h, it
> > cannot be relocated to the irq directory. This is in sync with other
> > backend directories like amd and intel there.
> >
> > Lastly, this file should not be tied to CONFIG_HYPERV_IOMMU, but to
> > CONFIG_HYPERV and CONFIG_IRQ_REMAP.
> >
> > Signed-off-by: Mukesh R <mrathor@linux.microsoft.com>
> > ---
> > V2: rename hv-irq-remap.c to hv-irq-remap-x86.c
> > ---
[...]
> Other than the above nits, feel free to add:
> Reviewed-by: Jacob Pan <jacob.pan@linux.microsoft.com>
I massaged the commit message, dropped the spurious white space changes,
and committed this patch.
Wei
next prev parent reply other threads:[~2026-06-08 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 22:50 Mukesh R
2026-06-03 23:56 ` Jacob Pan
2026-06-08 5:58 ` Wei Liu [this message]
2026-06-12 15:49 ` Easwar Hariharan
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=20260608055824.GA1555293@liuwe-devbox-debian-v2.local \
--to=wei.liu@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jacob.pan@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=mrathor@linux.microsoft.com \
--cc=schakrabarti@linux.microsoft.com \
--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
all inboxes | Powered by JetHome®