From: Paul Walmsley <pjw@kernel.org>
To: Ruidong Tian <tianruidong@linux.alibaba.com>, hchauhan@ventanamicro.com
Cc: xueshuai@linux.alibaba.com, palmer@dabbelt.com,
paul.walmsley@sifive.com, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
james.morse@arm.com, tony.luck@intel.com, cleger@rivosinc.com
Subject: Re: [RFC PATCH 1/5] riscv: Define ioremap_cache for RISC-V
Date: Wed, 17 Sep 2025 11:23:49 -0600 (MDT) [thread overview]
Message-ID: <f15b08a6-84f5-1e5c-79cd-a178037a2f11@kernel.org> (raw)
In-Reply-To: <20250910093347.75822-2-tianruidong@linux.alibaba.com>
On Wed, 10 Sep 2025, Ruidong Tian wrote:
> From: Himanshu Chauhan <hchauhan@ventanamicro.com>
>
> bert and einj drivers use ioremap_cache for mapping entries
> but ioremap_cache is not defined for RISC-V.
>
> Signed-off-by: Himanshu Chauhan <hchauhan@ventanamicro.com>
Looks like nothing should be using ioremap_cache() at all:
https://lore.kernel.org/linux-riscv/YzQ6pqykLhJVeD2p@infradead.org/#t
Probably best just to fix the ACPI drivers?
- Paul
next prev parent reply other threads:[~2025-09-17 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 9:33 [RFC PATCH 0/5] riscv: Handle synchronous hardware error exception Ruidong Tian
2025-09-10 9:33 ` [RFC PATCH 1/5] riscv: Define ioremap_cache for RISC-V Ruidong Tian
2025-09-17 17:23 ` Paul Walmsley [this message]
2025-09-10 9:33 ` [RFC PATCH 2/5] riscv: Define arch_apei_get_mem_attribute " Ruidong Tian
2025-09-10 9:33 ` [RFC PATCH 3/5] acpi: Introduce SSE and HEE in HEST notification types Ruidong Tian
2025-09-10 9:33 ` [RFC PATCH 4/5] riscv: Introduce HEST HEE notification handlers for APEI Ruidong Tian
2025-09-10 9:33 ` [RFC PATCH 5/5] riscv: Add Hardware Error Exception trap handler Ruidong Tian
2025-09-10 17:20 ` [RFC PATCH 0/5] riscv: Handle synchronous hardware error exception Anup Patel
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=f15b08a6-84f5-1e5c-79cd-a178037a2f11@kernel.org \
--to=pjw@kernel.org \
--cc=cleger@rivosinc.com \
--cc=hchauhan@ventanamicro.com \
--cc=james.morse@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=tianruidong@linux.alibaba.com \
--cc=tony.luck@intel.com \
--cc=xueshuai@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).