linux-kernel - Re: [PATCH] RISC-V: Don't print details of CPUs disabled in DT

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] [day] [month] [year] [list]

Message-Id: 
 <176080329574.3028979.687307160089751894.git-patchwork-notify@kernel.org>
Date: Sat, 18 Oct 2025 16:01:35 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Anup Patel <apatel@...tanamicro.com>
Cc: linux-riscv@...ts.infradead.org, palmer@...belt.com,
 paul.walmsley@...ive.com, alex@...ti.fr, atish.patra@...ux.dev,
 ajones@...tanamicro.com, anup@...infault.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] RISC-V: Don't print details of CPUs disabled in DT

Hello:

This patch was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@...nel.org>:

On Tue, 14 Oct 2025 22:00:09 +0530 you wrote:
> Early boot stages may disable CPU DT nodes for unavailable
> CPUs based on SKU, pinstraps, eFuse, etc. Currently, the
> riscv_early_of_processor_hartid() prints details of a CPU
> if it is disabled in DT which has no value and gives a
> false impression to the users that there some issue with
> the CPU.
> 
> [...]

Here is the summary with links:
  - RISC-V: Don't print details of CPUs disabled in DT
    https://git.kernel.org/riscv/c/d2721bb165b3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html