public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] [PULL REQUEST] Intel IOMMU updates for Linux v6.8
Date: Mon, 18 Dec 2023 15:34:41 +0800	[thread overview]
Message-ID: <20231218073445.142401-1-baolu.lu@linux.intel.com> (raw)

Hi Joerg,

The following patches have been queued for v6.8:

 - Cleanup and refactoring

All patches are based on v6.7-rc6. The series is also available at:
https://github.com/LuBaolu/intel-iommu/commits/vtd-update-for-v6.8

Please consider them for the next branch.

Best regards,
Baolu

Lu Baolu (4):
  iommu/vt-d: Refactor device_to_iommu() to retrieve iommu directly
  iommu/vt-d: Remove unused parameter of
    intel_pasid_setup_pass_through()
  iommu/vt-d: Remove unused vcmd interfaces
  iommu/vt-d: Move inline helpers to header files

 drivers/iommu/intel/iommu.h   | 179 +++++++++++++++++++++-
 drivers/iommu/intel/pasid.h   | 223 +++++++++++++++++++++++++--
 drivers/iommu/intel/debugfs.c |   3 -
 drivers/iommu/intel/iommu.c   | 239 +++--------------------------
 drivers/iommu/intel/pasid.c   | 274 +---------------------------------
 drivers/iommu/intel/svm.c     |  20 +--
 6 files changed, 415 insertions(+), 523 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-12-18  7:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18  7:34 Lu Baolu [this message]
2023-12-18  7:34 ` [PATCH 1/4] iommu/vt-d: Refactor device_to_iommu() to retrieve iommu directly Lu Baolu
2023-12-18  7:34 ` [PATCH 2/4] iommu/vt-d: Remove unused parameter of intel_pasid_setup_pass_through() Lu Baolu
2023-12-18  7:34 ` [PATCH 3/4] iommu/vt-d: Remove unused vcmd interfaces Lu Baolu
2023-12-18  7:34 ` [PATCH 4/4] iommu/vt-d: Move inline helpers to header files Lu Baolu
2023-12-19 13:34 ` [PATCH 0/4] [PULL REQUEST] Intel IOMMU updates for Linux v6.8 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=20231218073445.142401-1-baolu.lu@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --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