linux-kernel - Re: [PATCH] riscv: mm: Define MAX_POSSIBLE_PHYSMEM

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: 
 <176080329124.3028979.1869728422063945538.git-patchwork-notify@kernel.org>
Date: Sat, 18 Oct 2025 16:01:31 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Samuel Holland <samuel.holland@...ive.com>
Cc: linux-riscv@...ts.infradead.org, pjw@...nel.org, palmer@...belt.com,
 aou@...s.berkeley.edu, alex@...ti.fr, apopple@...dia.com,
 akpm@...ux-foundation.org, willy@...radead.org, will@...nel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] riscv: mm: Define MAX_POSSIBLE_PHYSMEM_BITS for zsmalloc

Hello:

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

On Wed, 15 Oct 2025 16:33:24 -0700 you wrote:
> This definition is used by zsmalloc to optimize memory allocation. On
> riscv64, it is the same as MAX_PHYSMEM_BITS from asm/sparsemem.h, but
> that definition depends on CONFIG_SPARSEMEM. The correct definition is
> already provided for riscv32.
> 
> Signed-off-by: Samuel Holland <samuel.holland@...ive.com>
> 
> [...]

Here is the summary with links:
  - riscv: mm: Define MAX_POSSIBLE_PHYSMEM_BITS for zsmalloc
    https://git.kernel.org/riscv/c/5898fc01ff34

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