From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Conor Dooley <conor.dooley@microchip.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
<linux-renesas-soc@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <linuxarm@huawei.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: [PATCH 0/2] riscv: Fix missing select CACHEMAINT_FOR_DMA
Date: Wed, 10 Dec 2025 16:00:45 +0000 [thread overview]
Message-ID: <20251210160047.201379-1-Jonathan.Cameron@huawei.com> (raw)
The drivers/cache/Kconfig menu was changed to a menuconfig so as to be able
to hide the menu for non RISCV. The select of drivers under the original
menu were broken as the menuconfig itself could be disabled. Fix this by
adding SELECT CACHEMAINT_FOR_DMA alongside the driver specific symbol
selects.
Jonathan Cameron (2):
riscv: ERRATA_STARFIVE_JH7100: Fix missing dependency on new
CONFIG_CACHEMAINT_FOR_DMA
soc: renesas: Fix missing dependency on new CONFIG_CACHEMAINT_FOR_DMA
arch/riscv/Kconfig.errata | 1 +
drivers/soc/renesas/Kconfig | 1 +
2 files changed, 2 insertions(+)
--
2.48.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2025-12-10 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 16:00 Jonathan Cameron [this message]
2025-12-10 16:00 ` [PATCH 1/2] riscv: ERRATA_STARFIVE_JH7100: Fix missing dependency on new CONFIG_CACHEMAINT_FOR_DMA Jonathan Cameron
2026-01-16 1:50 ` Paul Walmsley
2025-12-10 16:00 ` [PATCH 2/2] soc: renesas: " Jonathan Cameron
2025-12-16 14:25 ` Geert Uytterhoeven
2026-01-16 1:50 ` Paul Walmsley
2026-01-19 14:21 ` [PATCH 0/2] riscv: Fix missing select CACHEMAINT_FOR_DMA patchwork-bot+linux-riscv
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=20251210160047.201379-1-Jonathan.Cameron@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=conor.dooley@microchip.com \
--cc=fazilyildiran@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=magnus.damm@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul@pgazz.com \
--cc=pjw@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