From: Stephen Boyd <sboyd@kernel.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>,
andrew@lunn.c, gregory.clement@bootlin.co,
linux-clk@vger.kernel.org, mturquette@baylibre.com,
sebastian.hesselbarth@gmail.com
Cc: linux-arm-kernel@lists.infradead.org,
Ben Dooks <ben.dooks@codethink.co.uk>
Subject: Re: [PATCH] clk: mvebu: armada-37xx-periph: fix __iomem casts in structure init
Date: Mon, 23 Mar 2026 17:17:24 -0700 [thread overview]
Message-ID: <177431144473.5403.9307921610502647121@lazor> (raw)
In-Reply-To: <20260310123625.163846-1-ben.dooks@codethink.co.uk>
Quoting Ben Dooks (2026-03-10 05:36:25)
> There are a number of casts to "void __iomem *" in the initialsation
> of the driver's clk information. Fix this by adding a helper macro
> for the cast.
>
> Silences a number of sparse warnings:
>
> drivers/clk/mvebu/armada-37xx-periph.c:254:1: warning: incorrect type in initializer (different address spaces)
> drivers/clk/mvebu/armada-37xx-periph.c:254:1: expected void [noderef] __iomem *reg
> drivers/clk/mvebu/armada-37xx-periph.c:254:1: got void *
> drivers/clk/mvebu/armada-37xx-periph.c:254:1: warning: incorrect type in initializer (different address spaces)
> drivers/clk/mvebu/armada-37xx-periph.c:254:1: expected void [noderef] __iomem *reg1
> drivers/clk/mvebu/armada-37xx-periph.c:254:1: got void *
> drivers/clk/mvebu/armada-37xx-periph.c:254:1: warning: incorrect type in initializer (different address spaces)
> drivers/clk/mvebu/armada-37xx-periph.c:254:1: expected void [noderef] __iomem *reg2
> drivers/clk/mvebu/armada-37xx-periph.c:254:1: got void *
> drivers/clk/mvebu/armada-37xx-periph.c:255:1: warning: incorrect type in initializer (different address spaces)
> drivers/clk/mvebu/armada-37xx-periph.c:255:1: expected void [noderef] __iomem *reg
> drivers/clk/mvebu/armada-37xx-periph.c:255:1: got void *
> ...
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> ---
Applied to clk-next
prev parent reply other threads:[~2026-03-24 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 12:36 [PATCH] clk: mvebu: armada-37xx-periph: fix __iomem casts in structure init Ben Dooks
2026-03-10 13:28 ` Brian Masney
2026-03-24 0:17 ` Stephen Boyd [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=177431144473.5403.9307921610502647121@lazor \
--to=sboyd@kernel.org \
--cc=andrew@lunn.c \
--cc=ben.dooks@codethink.co.uk \
--cc=gregory.clement@bootlin.co \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sebastian.hesselbarth@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox