From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: "Pranjal Shrivastava" <praan@google.com>,
"Guanghui Feng" <guanghuifeng@linux.alibaba.com>,
"Michał Grzelak" <michal.grzelak@intel.com>,
"Michael Bommarito" <michael.bommarito@gmail.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] [PULL REQUEST] Intel IOMMU updates for v7.2
Date: Thu, 4 Jun 2026 12:02:19 +0200 [thread overview]
Message-ID: <aiFNG6UH1qNzRW_1@8bytes.org> (raw)
In-Reply-To: <20260604060311.365074-1-baolu.lu@linux.intel.com>
On Thu, Jun 04, 2026 at 02:03:05PM +0800, Lu Baolu wrote:
> Guanghui Feng (1):
> iommu/vt-d: Improve IOMMU fault information
>
> Lu Baolu (1):
> iommu/vt-d: Avoid WARNING in sva unbind path
>
> Michael Bommarito (1):
> iommu/vt-d: Clear Present bit before tearing down scalable-mode
> context entry
>
> Michał Grzelak (1):
> iommu/vt-d: Remove typo from pasid_pte_config_nested()
>
> Pranjal Shrivastava (1):
> iommu/vt-d: Fix RB-tree corruption in probe error path
>
> drivers/iommu/intel/iommu.h | 11 +++++++++++
> drivers/iommu/intel/dmar.c | 9 ++++++---
> drivers/iommu/intel/iommu.c | 6 +++++-
> drivers/iommu/intel/pasid.c | 16 +++++++++-------
> drivers/iommu/intel/svm.c | 12 ++++--------
> 5 files changed, 35 insertions(+), 19 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2026-06-04 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 6:03 [PATCH v2 0/5] [PULL REQUEST] Intel IOMMU updates for v7.2 Lu Baolu
2026-06-04 6:03 ` [PATCH v2 1/5] iommu/vt-d: Avoid WARNING in sva unbind path Lu Baolu
2026-06-04 6:03 ` [PATCH v2 2/5] iommu/vt-d: Clear Present bit before tearing down scalable-mode context entry Lu Baolu
2026-06-04 6:03 ` [PATCH v2 3/5] iommu/vt-d: Remove typo from pasid_pte_config_nested() Lu Baolu
2026-06-04 6:03 ` [PATCH v2 4/5] iommu/vt-d: Improve IOMMU fault information Lu Baolu
2026-06-04 6:03 ` [PATCH v2 5/5] iommu/vt-d: Fix RB-tree corruption in probe error path Lu Baolu
2026-06-04 10:02 ` Joerg Roedel [this message]
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=aiFNG6UH1qNzRW_1@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=guanghuifeng@linux.alibaba.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.bommarito@gmail.com \
--cc=michal.grzelak@intel.com \
--cc=praan@google.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.