From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] [PULL REQUEST] Intel IOMMU updates for Linux v6.1
Date: Mon, 26 Sep 2022 14:15:42 +0200 [thread overview]
Message-ID: <YzGX7ri+CYTpKfeP@8bytes.org> (raw)
In-Reply-To: <20220923004206.3630441-1-baolu.lu@linux.intel.com>
Hi Baolu,
On Fri, Sep 23, 2022 at 08:42:00AM +0800, Lu Baolu wrote:
> Lu Baolu (5):
> iommu/vt-d: Remove unnecessary SVA data accesses in page fault path
> iommu/vt-d: Decouple PASID & PRI enabling from SVA
> iommu/vt-d: Remove pasid_set_eafe()
> iommu/vt-d: Avoid unnecessary global IRTE cache invalidation
> iommu/vt-d: Avoid unnecessary global DMA cache invalidation
>
> Yi Liu (1):
> iommu/vt-d: Rename cap_5lp_support to cap_fl5lp_support
These don't apply cleanly on v6.0-rc4 or -rc7. Please rebase these
patches to my x86/vt-d branch and re-send.
Thanks,
Joerg
next prev parent reply other threads:[~2022-09-26 12:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 0:42 [PATCH 0/6] [PULL REQUEST] Intel IOMMU updates for Linux v6.1 Lu Baolu
2022-09-23 0:42 ` [PATCH 1/6] iommu/vt-d: Remove unnecessary SVA data accesses in page fault path Lu Baolu
2022-09-23 0:42 ` [PATCH 2/6] iommu/vt-d: Decouple PASID & PRI enabling from SVA Lu Baolu
2022-09-23 0:42 ` [PATCH 3/6] iommu/vt-d: Remove pasid_set_eafe() Lu Baolu
2022-09-23 0:42 ` [PATCH 4/6] iommu/vt-d: Rename cap_5lp_support to cap_fl5lp_support Lu Baolu
2022-09-23 0:42 ` [PATCH 5/6] iommu/vt-d: Avoid unnecessary global IRTE cache invalidation Lu Baolu
2022-09-23 0:42 ` [PATCH 6/6] iommu/vt-d: Avoid unnecessary global DMA " Lu Baolu
2022-09-26 12:15 ` Joerg Roedel [this message]
2022-09-26 12:38 ` [PATCH 0/6] [PULL REQUEST] Intel IOMMU updates for Linux v6.1 Baolu Lu
2022-09-26 13:01 ` Joerg Roedel
2022-09-26 13:24 ` Baolu Lu
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=YzGX7ri+CYTpKfeP@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).