All of lore.kernel.org
 help / color / mirror / Atom feed
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/7] [PULL REQUEST] Intel IOMMU updates for Linux v6.2
Date: Tue, 22 Nov 2022 10:06:57 +0100	[thread overview]
Message-ID: <Y3yRMXGPcYbXH9uL@8bytes.org> (raw)
In-Reply-To: <20221122002949.148140-1-baolu.lu@linux.intel.com>

Hi Baolu,

On Tue, Nov 22, 2022 at 08:29:42AM +0800, Lu Baolu wrote:
> Lu Baolu (7):
>   iommu/vt-d: Allocate pasid table in device probe path
>   iommu/vt-d: Add device_block_translation() helper
>   iommu/vt-d: Add blocking domain support
>   iommu/vt-d: Rename iommu_disable_dev_iotlb()
>   iommu/vt-d: Rename domain_add_dev_info()
>   iommu/vt-d: Remove unnecessary domain_context_mapped()
>   iommu/vt-d: Use real field for indication of first level

Applied the first 6 patches. The last one has conflicts and doesn't
apply on top of my x86/vt-d branch. Could you please have a look please?

Thanks,

	Joerg

  parent reply	other threads:[~2022-11-22  9:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22  0:29 [PATCH 0/7] [PULL REQUEST] Intel IOMMU updates for Linux v6.2 Lu Baolu
2022-11-22  0:29 ` [PATCH 1/7] iommu/vt-d: Allocate pasid table in device probe path Lu Baolu
2022-11-22  0:29 ` [PATCH 2/7] iommu/vt-d: Add device_block_translation() helper Lu Baolu
2022-11-22  0:29 ` [PATCH 3/7] iommu/vt-d: Add blocking domain support Lu Baolu
2022-11-22  0:29 ` [PATCH 4/7] iommu/vt-d: Rename iommu_disable_dev_iotlb() Lu Baolu
2022-11-22  0:29 ` [PATCH 5/7] iommu/vt-d: Rename domain_add_dev_info() Lu Baolu
2022-11-22  0:29 ` [PATCH 6/7] iommu/vt-d: Remove unnecessary domain_context_mapped() Lu Baolu
2022-11-22  0:29 ` [PATCH 7/7] iommu/vt-d: Use real field for indication of first level Lu Baolu
2022-11-22  9:06 ` Joerg Roedel [this message]
2022-11-22  9:41   ` [PATCH 0/7] [PULL REQUEST] Intel IOMMU updates for Linux v6.2 Baolu Lu
2022-11-22 13:06     ` Joerg Roedel

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=Y3yRMXGPcYbXH9uL@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 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.