From: Zenghui Yu <yuzenghui@huawei.com>
To: <lorenzo.pieralisi@arm.com>, <guohanjun@huawei.com>,
<sudeep.holla@arm.com>
Cc: <linux-acpi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <wanghaibin.wang@huawei.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: [PATCH v2 2/2] ACPI/IORT: Remove the unused inline functions
Date: Tue, 18 Aug 2020 14:36:25 +0800 [thread overview]
Message-ID: <20200818063625.980-3-yuzenghui@huawei.com> (raw)
In-Reply-To: <20200818063625.980-1-yuzenghui@huawei.com>
Since commit 8212688600ed ("ACPI/IORT: Fix build error when IOMMU_SUPPORT
is disabled"), iort_fwspec_iommu_ops() and iort_add_device_replay() are not
needed anymore when CONFIG_IOMMU_API is not selected. Let's remove them.
Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
---
drivers/acpi/arm64/iort.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
index a0ece0e201b2..e670785a6201 100644
--- a/drivers/acpi/arm64/iort.c
+++ b/drivers/acpi/arm64/iort.c
@@ -1086,10 +1086,6 @@ const struct iommu_ops *iort_iommu_configure_id(struct device *dev,
}
#else
-static inline const struct iommu_ops *iort_fwspec_iommu_ops(struct device *dev)
-{ return NULL; }
-static inline int iort_add_device_replay(struct device *dev)
-{ return 0; }
int iort_iommu_msi_get_resv_regions(struct device *dev, struct list_head *head)
{ return 0; }
const struct iommu_ops *iort_iommu_configure_id(struct device *dev,
--
2.19.1
next prev parent reply other threads:[~2020-08-18 6:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 6:36 [PATCH v2 0/2] ACPI/IORT: Code cleanups Zenghui Yu
2020-08-18 6:36 ` [PATCH v2 1/2] ACPI/IORT: Drop the unused @ops of iort_add_device_replay() Zenghui Yu
2020-08-18 6:36 ` Zenghui Yu [this message]
2020-08-18 9:16 ` [PATCH v2 0/2] ACPI/IORT: Code cleanups Hanjun Guo
2020-09-02 9:17 ` Hanjun Guo
2020-09-02 9:48 ` Will Deacon
2020-09-02 11:55 ` Hanjun Guo
2020-09-02 9:29 ` Lorenzo Pieralisi
2020-09-07 16:05 ` Will Deacon
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=20200818063625.980-3-yuzenghui@huawei.com \
--to=yuzenghui@huawei.com \
--cc=guohanjun@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sudeep.holla@arm.com \
--cc=wanghaibin.wang@huawei.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
all inboxes | Powered by JetHome®