From: Paul Walmsley <pjw@kernel.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
pjw@kernel.org, linux-kernel@vger.kernel.org, alex@ghiti.fr
Subject: Re: [PATCH] RISC-V: ACPI: fix two __iomem cast warnings
Date: Thu, 2 Apr 2026 15:31:51 -0600 (MDT) [thread overview]
Message-ID: <df1a84c9-e039-f81b-eb46-04203990981d@kernel.org> (raw)
In-Reply-To: <20260311102217.409376-1-ben.dooks@codethink.co.uk>
Hi Ben,
On Wed, 11 Mar 2026, Ben Dooks wrote:
> The __acpi_map_table() and __acpi_unmap_table() return and
> take __iomem tagged pointers. Add a cast to fix the sparse
> warnings:
>
> arch/riscv/kernel/acpi.c:216:30: warning: incorrect type in return expression (different address spaces)
> arch/riscv/kernel/acpi.c:216:30: expected void [noderef] __iomem *
> arch/riscv/kernel/acpi.c:216:30: got void *
> arch/riscv/kernel/acpi.c:224:24: warning: incorrect type in argument 1 (different address spaces)
> arch/riscv/kernel/acpi.c:224:24: expected void *addr
> arch/riscv/kernel/acpi.c:224:24: got void [noderef] __iomem *map
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
Thanks for taking a look at this. It appears that some of the other
architectures have the same issue. Could you come up with a series that
addresses the others as well? You might need to get the ACPI folks
involved; it's not really clear to me why __acpi_map_table() needs to
return an __iomem *.
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-04-02 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 10:22 [PATCH] RISC-V: ACPI: fix two __iomem cast warnings Ben Dooks
2026-04-02 21:31 ` Paul Walmsley [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=df1a84c9-e039-f81b-eb46-04203990981d@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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