From: "Yong Wu (吴勇)" <Yong.Wu@mediatek.com>
To: "robin.murphy@arm.com" <robin.murphy@arm.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"will@kernel.org" <will@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"krzysztof.kozlowski@linaro.org" <krzysztof.kozlowski@linaro.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>
Subject: Re: [PATCH] iommu/mediatek-v1: Tidy up probe_finalize
Date: Sat, 28 Jun 2025 08:09:10 +0000 [thread overview]
Message-ID: <26474a6747afc1e018a2c99fc5589ef545a26bea.camel@mediatek.com> (raw)
In-Reply-To: <7c78149504900bc6c98a9c48f4418934b72d89ac.1751036478.git.robin.murphy@arm.com>
On Fri, 2025-06-27 at 16:07 +0100, Robin Murphy wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> Krzysztof points out that although the driver now supports
> COMPILE_TEST
> for other architectures, it does not build cleanly with W=1 where the
> stubbed-out ARM API can lead to an unused variable warning.
>
> Since this is effectively the correct intent of the code in such
> cases,
> mark it as __maybe_unused, tidying up some cruft in the process.
>
> Reported-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Reviewed-by: Yong Wu <yong.wu@mediatek.com>
> ---
>
> Since I'd already got as far as thinking this through, I figure I may
> as well save Krzysztof the trouble of rewriting it :)
>
> drivers/iommu/mtk_iommu_v1.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iommu/mtk_iommu_v1.c
> b/drivers/iommu/mtk_iommu_v1.c
> index 66824982e05f..2fc18e194e19 100644
> --- a/drivers/iommu/mtk_iommu_v1.c
> +++ b/drivers/iommu/mtk_iommu_v1.c
> @@ -509,14 +509,10 @@ static struct iommu_device
> *mtk_iommu_v1_probe_device(struct device *dev)
>
> static void mtk_iommu_v1_probe_finalize(struct device *dev)
> {
> - struct dma_iommu_mapping *mtk_mapping;
> - struct mtk_iommu_v1_data *data;
> + __maybe_unused struct mtk_iommu_v1_data *data =
> dev_iommu_priv_get(dev);
> int err;
>
> - data = dev_iommu_priv_get(dev);
> - mtk_mapping = data->mapping;
> -
> - err = arm_iommu_attach_device(dev, mtk_mapping);
> + err = arm_iommu_attach_device(dev, data->mapping);
> if (err)
> dev_err(dev, "Can't create IOMMU mapping - DMA-OPS
> will not work\n");
> }
> --
> 2.39.2.101.g768bb238c484.dirty
>
next prev parent reply other threads:[~2025-06-28 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 15:07 [PATCH] iommu/mediatek-v1: Tidy up probe_finalize Robin Murphy
2025-06-28 8:09 ` Yong Wu (吴勇) [this message]
2025-06-28 8:36 ` Krzysztof Kozlowski
2025-07-04 8:33 ` 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=26474a6747afc1e018a2c99fc5589ef545a26bea.camel@mediatek.com \
--to=yong.wu@mediatek.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--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