From: Antonio Borneo <antonio.borneo@foss.st.com>
To: Bjorn Andersson <andersson@kernel.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
<linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Antonio Borneo <antonio.borneo@foss.st.com>
Subject: [PATCH] hwspinlock: fix warning from sparse
Date: Mon, 23 Mar 2026 11:22:10 +0100 [thread overview]
Message-ID: <20260323102210.228551-1-antonio.borneo@foss.st.com> (raw)
Sparse triggers the following warnings:
drivers/hwspinlock/hwspinlock_core.c:392:9: warning: incorrect type in assignment (different address spaces)
drivers/hwspinlock/hwspinlock_core.c:392:9: expected void **slot
drivers/hwspinlock/hwspinlock_core.c:392:9: got void [noderef] __rcu **
drivers/hwspinlock/hwspinlock_core.c:392:9: warning: incorrect type in assignment (different address spaces)
drivers/hwspinlock/hwspinlock_core.c:392:9: expected void **slot
drivers/hwspinlock/hwspinlock_core.c:392:9: got void [noderef] __rcu **
drivers/hwspinlock/hwspinlock_core.c:393:48: warning: incorrect type in argument 1 (different address spaces)
drivers/hwspinlock/hwspinlock_core.c:393:48: expected void [noderef] __rcu **slot
drivers/hwspinlock/hwspinlock_core.c:393:48: got void **slot
drivers/hwspinlock/hwspinlock_core.c:397:30: warning: incorrect type in assignment (different address spaces)
drivers/hwspinlock/hwspinlock_core.c:397:30: expected void **slot
drivers/hwspinlock/hwspinlock_core.c:397:30: got void [noderef] __rcu **
drivers/hwspinlock/hwspinlock_core.c:392:9: warning: incorrect type in argument 1 (different address spaces)
drivers/hwspinlock/hwspinlock_core.c:392:9: expected void [noderef] __rcu **slot
drivers/hwspinlock/hwspinlock_core.c:392:9: got void **slot
drivers/hwspinlock/hwspinlock_core.c:392:9: warning: incorrect type in assignment (different address spaces)
drivers/hwspinlock/hwspinlock_core.c:392:9: expected void **slot
drivers/hwspinlock/hwspinlock_core.c:392:9: got void [noderef] __rcu **
all linked to the same missing '__rcu' at declaration of 'slot'.
Fix it!
Signed-off-by: Antonio Borneo <antonio.borneo@foss.st.com>
---
drivers/hwspinlock/hwspinlock_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwspinlock/hwspinlock_core.c b/drivers/hwspinlock/hwspinlock_core.c
index cc8e952a67727..50a875b2353f8 100644
--- a/drivers/hwspinlock/hwspinlock_core.c
+++ b/drivers/hwspinlock/hwspinlock_core.c
@@ -372,7 +372,7 @@ int of_hwspin_lock_get_id(struct device_node *np, int index)
struct of_phandle_args args;
struct hwspinlock *hwlock;
struct radix_tree_iter iter;
- void **slot;
+ void __rcu **slot;
int id;
int ret;
base-commit: c369299895a591d96745d6492d4888259b004a9e
--
2.34.1
next reply other threads:[~2026-03-23 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 10:22 Antonio Borneo [this message]
2026-03-25 8:53 ` [PATCH] hwspinlock: fix warning from sparse Antonio Borneo
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=20260323102210.228551-1-antonio.borneo@foss.st.com \
--to=antonio.borneo@foss.st.com \
--cc=andersson@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@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 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.