From: patchwork-bot+linux-riscv@kernel.org
To: Dimitris Vlachos <dvlachos@ics.forth.gr>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
palmer@dabbelt.com, alexghiti@rivosinc.com,
paul.walmsley@sifive.com, clameter@sgi.com,
akpm@linux-foundation.org, rppt@kernel.org, arnd@arndb.de,
mick@ics.forth.gr, csd4492@csd.uoc.gr, maraz@ics.forth.gr
Subject: Re: [PATCH -fixes v2] riscv: Sparse-Memory/vmemmap out-of-bounds fix
Date: Thu, 29 Feb 2024 22:10:34 +0000 [thread overview]
Message-ID: <170924463471.14902.12448827543196020525.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240229191723.32779-1-dvlachos@ics.forth.gr>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 29 Feb 2024 21:17:23 +0200 you wrote:
> Offset vmemmap so that the first page of vmemmap will be mapped
> to the first page of physical memory in order to ensure that
> vmemmap’s bounds will be respected during
> pfn_to_page()/page_to_pfn() operations.
> The conversion macros will produce correct SV39/48/57 addresses
> for every possible/valid DRAM_BASE inside the physical memory limits.
>
> [...]
Here is the summary with links:
- [-fixes,v2] riscv: Sparse-Memory/vmemmap out-of-bounds fix
https://git.kernel.org/riscv/c/a11dd49dcb93
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-02-29 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 19:17 [PATCH -fixes v2] riscv: Sparse-Memory/vmemmap out-of-bounds fix Dimitris Vlachos
2024-02-29 22:10 ` patchwork-bot+linux-riscv [this message]
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=170924463471.14902.12448827543196020525.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=arnd@arndb.de \
--cc=clameter@sgi.com \
--cc=csd4492@csd.uoc.gr \
--cc=dvlachos@ics.forth.gr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maraz@ics.forth.gr \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rppt@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