From: Joerg Roedel <joro@8bytes.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: will@kernel.org, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, yong.wu@mediatek.com,
thierry.reding@gmail.com, vdumpa@nvidia.com
Subject: Re: [PATCH] iommu: Unexport iommu_fwspec_free()
Date: Tue, 11 Mar 2025 14:15:04 +0100 [thread overview]
Message-ID: <Z9A3WJSgUPjROev6@8bytes.org> (raw)
In-Reply-To: <36e245489361de2d13db22a510fa5c79e7126278.1740667667.git.robin.murphy@arm.com>
This patch triggered two compile issues on ARM32, which I fixed up in my
tree:
On Thu, Feb 27, 2025 at 02:47:47PM +0000, Robin Murphy wrote:
> static struct iommu_device *mtk_iommu_v1_probe_device(struct device *dev)
> {
> - struct iommu_fwspec *fwspec = dev_iommu_fwspec_get(dev);
> + struct iommu_fwspec *fwspec = NULL
Missing semicolon here.
> struct of_phandle_args iommu_spec;
> struct mtk_iommu_v1_data *data;
> int err, idx = 0, larbid, larbidx;
> struct device_link *link;
> struct device *larbdev;
>
> - /*
> - * In the deferred case, free the existed fwspec.
> - * Always initialize the fwspec internally.
> - */
> - if (fwspec) {
> - iommu_fwspec_free(dev);
> - fwspec = dev_iommu_fwspec_get(dev);
> - }
> -
> while (!of_parse_phandle_with_args(dev->of_node, "iommus",
> "#iommu-cells",
> idx, &iommu_spec)) {
> @@ -476,6 +467,9 @@ static struct iommu_device *mtk_iommu_v1_probe_device(struct device *dev)
> idx++;
> }
>
> + if (!fwspec)
> + return -ENODEV;
> +
Wrong return type here.
Please be more cautious next time and make sure to compile-test all
changed files of a patch.
Thanks,
Joerg
next prev parent reply other threads:[~2025-03-11 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 14:47 [PATCH] iommu: Unexport iommu_fwspec_free() Robin Murphy
2025-03-05 18:29 ` Jason Gunthorpe
2025-03-10 8:26 ` Joerg Roedel
2025-03-11 13:15 ` Joerg Roedel [this message]
2025-03-11 14:21 ` Robin Murphy
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=Z9A3WJSgUPjROev6@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@arm.com \
--cc=thierry.reding@gmail.com \
--cc=vdumpa@nvidia.com \
--cc=will@kernel.org \
--cc=yong.wu@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.