linux-kernel - Re: [PATCH] clk: COMMON_CLK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6555b47f-919b-b56c-4a76-352c904343c2@kernel.org>
Date: Wed, 1 Oct 2025 19:15:56 -0600 (MDT)
From: Paul Walmsley <pjw@...nel.org>
To: Geert Uytterhoeven <geert+renesas@...der.be>
cc: Michael Turquette <mturquette@...libre.com>, 
    Stephen Boyd <sboyd@...nel.org>, Rahul Pathak <rpathak@...tanamicro.com>, 
    Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
    Anup Patel <apatel@...tanamicro.com>, Paul Walmsley <pjw@...nel.org>, 
    linux-clk@...r.kernel.org, linux-riscv@...ts.infradead.org, 
    linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clk: COMMON_CLK_RPMI should depend on RISCV

On Tue, 30 Sep 2025, Geert Uytterhoeven wrote:

> The RISC-V platform management interface (RPMI) is only available on
> RISC-V platforms.  Hence add a dependency on RISCV, to prevent asking
> the user about this driver when configuring a kernel for a different
> architecture.
> 
> Fixes: 5ba9f520f41a33c9 ("clk: Add clock driver for the RISC-V RPMI clock service group")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>

Thanks Geert for catching this.

This patch is against unmerged patches in -next.  So I'll plan to add this 
to the PR that I plan to send to Linus tomorrow -- unless any of the 
drivers/clk maintainers would prefer that I not.

> And perhaps the "default RISCV" should be dropped, too?

Probably.  I guess we should just add this to the arch/riscv defconfig 
instead.  Let's wait on this one for a few days to see if anyone has any 
comments, and consider that change for v6.18-rc fixes.

thanks again,

- Paul