From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: m.szyprowski@samsung.com, joro@8bytes.org
Cc: will@kernel.org, robin.murphy@arm.com,
krzysztof.kozlowski@linaro.org, alim.akhtar@samsung.com,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Tudor Ambarus <tudor.ambarus@linaro.org>
Subject: [PATCH] iommu/exynos: trivial use of local dev variable
Date: Fri, 3 May 2024 08:27:20 +0000 [thread overview]
Message-ID: <20240503082720.966423-1-tudor.ambarus@linaro.org> (raw)
exynos_sysmmu_probe() defines:
struct device *dev = &pdev->dev;
then initializes:
data->sysmmu = dev;
Replace further &pdev->dev and data->sysmmu use with dev.
Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
---
drivers/iommu/exynos-iommu.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/exynos-iommu.c b/drivers/iommu/exynos-iommu.c
index d98c9161948a..447cf0d07625 100644
--- a/drivers/iommu/exynos-iommu.c
+++ b/drivers/iommu/exynos-iommu.c
@@ -774,8 +774,7 @@ static int exynos_sysmmu_probe(struct platform_device *pdev)
__sysmmu_get_version(data);
- ret = iommu_device_sysfs_add(&data->iommu, &pdev->dev, NULL,
- dev_name(data->sysmmu));
+ ret = iommu_device_sysfs_add(&data->iommu, dev, NULL, dev_name(dev));
if (ret)
return ret;
@@ -806,7 +805,7 @@ static int exynos_sysmmu_probe(struct platform_device *pdev)
* dma mapping operations on iommu page tables (cpu cache flush)
*/
if (!dma_dev)
- dma_dev = &pdev->dev;
+ dma_dev = dev;
pm_runtime_enable(dev);
--
2.45.0.rc1.225.g2a3ae87e7f-goog
reply other threads:[~2024-05-03 8:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240503082720.966423-1-tudor.ambarus@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=will@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 read-only IMAP folder(s) and NNTP newsgroup(s).