From: Lu Baolu <baolu.lu@linux.intel.com>
To: iommu@lists.linux.dev
Cc: Joerg Roedel <joro@8bytes.org>, Kevin Tian <kevin.tian@intel.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Liu Yi L <yi.l.liu@intel.com>,
Jacob jun Pan <jacob.jun.pan@intel.com>,
linux-kernel@vger.kernel.org, Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH v2 6/8] iommu/vt-d: Rename domain_add_dev_info()
Date: Tue, 8 Nov 2022 15:34:06 +0800 [thread overview]
Message-ID: <20221108073408.1005721-7-baolu.lu@linux.intel.com> (raw)
In-Reply-To: <20221108073408.1005721-1-baolu.lu@linux.intel.com>
dmar_domain_attach_device() is more meaningful according to what this
helper does.
Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
---
drivers/iommu/intel/iommu.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
index 8bbe516f7d21..88af8e4194de 100644
--- a/drivers/iommu/intel/iommu.c
+++ b/drivers/iommu/intel/iommu.c
@@ -2492,7 +2492,8 @@ static int __init si_domain_init(int hw)
return 0;
}
-static int domain_add_dev_info(struct dmar_domain *domain, struct device *dev)
+static int dmar_domain_attach_device(struct dmar_domain *domain,
+ struct device *dev)
{
struct device_domain_info *info = dev_iommu_priv_get(dev);
struct intel_iommu *iommu;
@@ -4298,7 +4299,7 @@ static int intel_iommu_attach_device(struct iommu_domain *domain,
if (ret)
return ret;
- return domain_add_dev_info(to_dmar_domain(domain), dev);
+ return dmar_domain_attach_device(to_dmar_domain(domain), dev);
}
static int intel_iommu_map(struct iommu_domain *domain,
--
2.34.1
next prev parent reply other threads:[~2022-11-08 7:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 7:34 [PATCH v2 0/8] iommu/vt-d: Some cleanups Lu Baolu
2022-11-08 7:34 ` [PATCH v2 1/8] iommu/vt-d: Allocate pasid table in device probe path Lu Baolu
2022-11-08 7:34 ` [PATCH v2 2/8] iommu/vt-d: Improve iommu_enable_pci_caps() Lu Baolu
2022-11-11 3:45 ` Tian, Kevin
2022-11-11 6:59 ` Baolu Lu
2022-11-11 8:16 ` Tian, Kevin
2022-11-11 11:57 ` Baolu Lu
2022-11-08 7:34 ` [PATCH v2 3/8] iommu/vt-d: Add device_block_translation() helper Lu Baolu
2022-11-08 7:34 ` [PATCH v2 4/8] iommu/vt-d: Add blocking domain support Lu Baolu
2022-11-08 7:34 ` [PATCH v2 5/8] iommu/vt-d: Fold dmar_remove_one_dev_info() into its caller Lu Baolu
2022-11-08 7:34 ` Lu Baolu [this message]
2022-11-08 7:34 ` [PATCH v2 7/8] iommu/vt-d: Remove unnecessary domain_context_mapped() Lu Baolu
2022-11-08 7:34 ` [PATCH v2 8/8] iommu/vt-d: Use real field for indication of first level Lu Baolu
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=20221108073408.1005721-7-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.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