From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Ben Dooks <ben.dooks@codethink.co.uk>
Subject: Re: [PATCH] soc: qcom: smsm: fix __iomem annotations
Date: Mon, 31 Aug 2026 15:21:13 -0500 [thread overview]
Message-ID: <178820768637.1699313.9062409495494007745.b4-ty@kernel.org> (raw)
In-Reply-To: <20260623090954.620688-1-ben.dooks@codethink.co.uk>
On Tue, 23 Jun 2026 10:09:54 +0100, Ben Dooks wrote:
> There are a number of points in the driver which miss out
> on __iomem annotations, so add these to remove the following
> sparse warnings:
>
> drivers/soc/qcom/smsm.c:159:32: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:159:32: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:159:32: got unsigned int [usertype] *local_state
> drivers/soc/qcom/smsm.c:171:25: warning: incorrect type in argument 2 (different address spaces)
> drivers/soc/qcom/smsm.c:171:25: expected void volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:171:25: got unsigned int [usertype] *local_state
> drivers/soc/qcom/smsm.c:181:48: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:181:48: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:181:48: got unsigned int [usertype] *
> drivers/soc/qcom/smsm.c:219:26: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:219:26: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:219:26: got unsigned int [usertype] *remote_state
> drivers/soc/qcom/smsm.c:257:49: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:257:49: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:257:49: got unsigned int [usertype] *
> drivers/soc/qcom/smsm.c:259:49: warning: incorrect type in argument 2 (different address spaces)
> drivers/soc/qcom/smsm.c:259:49: expected void volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:259:49: got unsigned int [usertype] *
> drivers/soc/qcom/smsm.c:280:24: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:280:24: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:280:24: got unsigned int [usertype] *remote_state
> drivers/soc/qcom/smsm.c:288:49: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:288:49: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:288:49: got unsigned int [usertype] *
> drivers/soc/qcom/smsm.c:290:49: warning: incorrect type in argument 2 (different address spaces)
> drivers/soc/qcom/smsm.c:290:49: expected void volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:290:49: got unsigned int [usertype] *
> drivers/soc/qcom/smsm.c:330:26: warning: incorrect type in argument 1 (different address spaces)
> drivers/soc/qcom/smsm.c:330:26: expected void const volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:330:26: got unsigned int [usertype] *remote_state
> drivers/soc/qcom/smsm.c:635:47: warning: incorrect type in argument 2 (different address spaces)
> drivers/soc/qcom/smsm.c:635:47: expected void volatile [noderef] __iomem *addr
> drivers/soc/qcom/smsm.c:635:47: got unsigned int [usertype] *
>
> [...]
Applied, thanks!
[1/1] soc: qcom: smsm: fix __iomem annotations
commit: c84cdd308471d6ae4f8121660436a4fed8126709
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-08-31 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 9:09 Ben Dooks
2026-08-31 20:21 ` Bjorn Andersson [this message]
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=178820768637.1699313.9062409495494007745.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=ben.dooks@codethink.co.uk \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®